home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ShareWare OnLine 2
/
ShareWare OnLine Volume 2 (CMS Software)(1993).iso
/
bbs_soft
/
sf33_2.zip
/
SF33DOCS.ZIP
/
SPITFIRE.DOC
< prev
Wrap
Text File
|
1993-03-03
|
514KB
|
9,081 lines
_________________________________________________________________________
___________________ ___________________
________________ S P I T F I R E ________________
_____________ ------------------------- _____________
__________ Bulletin Board System __________
_______ for MS/PC DOS _______
____ Personal Computers ____
_______________________________
____ ____
____ Version 3.3 ____
___________________
Copyright (C) 1987-1993 by Mike Woltz
-------------------------------------
Buffalo Creek Software
------------------------------------------
>>> Release Date March 3, 1993 <<<
------------------------------------------
TABLE OF CONTENTS
---------------------
# Section Title Page #
+--+------------------------------------------------+------+
Introduction.......................................... 1
<1> 1.0 Important Notice................................. 1
1.1 Copyright & Registered Trademark Notice.......... 2
<2> 2.0 SPITFIRE Hardware Requirements................... 3
2.1 Modems........................................... 4
2.2 Modem Initialization............................. 5
<3> 3.0 Getting Started.................................. 6
<4> 4.0 SPITFIRE File Paths............................. 20
4.1 SPITFIRE System Files........................... 21
4.2 SPITFIRE Message Files.......................... 24
4.3 SPITFIRE Work Files............................. 24
4.4 SPITFIRE Display Files.......................... 25
4.5 SPITFIRE Menu Files............................. 29
4.6 SPITFIRE File Clarifications.................... 32
4.7 About SPITFIRE Display Files.................... 40
4.8 Backup Files.................................... 42
4.9 THOUGHTS.BBS.................................... 42
<5> 5.0 Command Line Parameters......................... 42
5.1 SF.BAT.......................................... 44
<6> 6.0 Setting Up the System Records................... 44
6.1 Configuring Message Conference Records.......... 44
6.2 Configuring File Area Records................... 50
<7> 7.0 SPITFIRE Questionnaires......................... 54
<8> 8.0 Special Function Keys........................... 58
8.1 Available Special Function Keys................. 58
8.2 Special Function Key Definitions................ 59
<9> 9.0 Main Section Explained.......................... 72
9.1 Main Menu Example............................... 72
9.2 Explanation of Main Menu Features............... 73
<10> 10.0 Message Section Explained....................... 77
10.1 Message Menu Example............................ 78
10.2 Message Menu Explanation........................ 78
<11> 11.0 File Section Explained.......................... 89
11.1 File Menu Example............................... 90
11.2 File Menu Explanation........................... 90
11.3 Upload/Download Protocols....................... 98
11.4 Batch Download Menu............................. 99
11.5 Batch Upload Menu.............................. 100
<12> 12.0 Sysop Section Explained........................ 102
12.1 Sysop Menu Explanation......................... 102
TABLE OF CONTENTS (cont)
------------------------
# Section Title Page #
+--+------------------------------------------------+------+
<13> 13.0 Special Commands for Sysop Status.............. 107
13.1 Special Commands for Sysop..................... 108
<14> 14.0 Events Menu Example............................ 109
14.1 Events Menu Explanation........................ 109
<15> 15.0 Hardware/Software Data Flow Control............ 113
<16> 16.0 Screen Save Features........................... 113
<17> 17.0 SPITFIRE Doors Section......................... 114
17.1 SPITFIRE Doors Display Files................... 116
17.2 SPITFIRE Doors Support......................... 117
<18> 18.0 External File Transfer Protocols............... 118
18.1 External Download Protocols.................... 118
18.2 External Batch Download Protocols.............. 121
18.3 Text File External Batch Download Protocols.... 122
18.4 External Upload Protocols...................... 123
18.5 External Batch Upload Protocols................ 126
18.6 Bi-Directional Protocol File Transfers......... 127
18.7 External Protocol Support...................... 130
<19> 19.0 SPITFIRE Utilizes EMS.......................... 130
<20> 20.0 SPITFIRE Net-Mail Capabilities................. 130
<21> 21.0 Operating A Multi-Node SPITFIRE................ 131
21.1 Multi-Node BBS Requirements.................... 131
21.2 Configuring SPITFIRE For Multi-Node Operation.. 132
21.3 Features Unique To Multi-Node Operation........ 132
21.4 Node Chat...................................... 133
<22> 22.0 SPITFIRE Multi-Tasking/Network Environment..... 136
<23> 23.0 SPITFIRE Technical Reference Information ...... 136
<24> 24.0 SPITFIRE Companion Programs ................... 137
24.1 DAILYLMT....................................... 137
24.2 SFDOOR......................................... 137
24.3 SFSENDIT....................................... 138
24.4 LAKOTA......................................... 138
24.5 SFPCKUSR....................................... 139
24.6 SFPCKMSG....................................... 140
<25> 25.0 Comment from the Author........................ 140
Appendix A Modem Initialization Strings................... 143
Appendix B SPITFIRE Questions and Answers................. 147
Subject Index............................................. 155
Page 1
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
-----------------------------------------------------------------------
INTRODUCTION
------------
SPITFIRE is a bulletin board program written in Borland's Turbo
Pascal and interfaced with assembler code compiled by Borland's Turbo
Assembler. Designed on an IBM Personal Computer, SPITFIRE is
compatible with MS/PC DOS machines (IBM "Compatibles").
SPITFIRE is distributed under the "Shareware" concept. You are
encouraged to distribute this software to others, in its original,
unmodified condition, as long as you DO NOT charge for this program
in any way, shape or form.
1.0 - IMPORTANT NOTICE!
-----------------------
Thank you for taking the time and expense to obtain SPITFIRE.
Surely, after you've had a chance to look SPITFIRE over, you'll agree
it is a powerful bulletin board program which combines both speed,
flexibility and user ease.
This program, like many others, is distributed under the
"Shareware" concept. SPITFIRE can be utilized on a trial basis for
not more than 30 days. In the event SPITFIRE is used beyond the trial
period, then a registration fee of $85.00 in "U.S. FUNDS" is required.
Please specify on your registration form whether you wish to receive
5 1/4" disks or 3 1/2" diskettes. If not specified, 3 1/2" disks will
be sent. If you live outside of the North American continent
(countries other than Canada, Mexico, the United States or provinces
of the United States) an addition $10 fee (i.e., $95.00) is required
for postage and handling.
Your registration of SPITFIRE will provide you with support and
notification of future updates and revisions of SPITFIRE. Any portion
of or all such support and notification may be changed and/or
terminated at any time without notice.
Many of you will be running SPITFIRE 24 hours per day, 7 days per
week. This is more than any other program you'll use. Considering
that, it becomes apparent that the registration fee is truly minimal.
|--------------------------------------------------------------------|
| Registration is simple & easy. Send the registration fee to: |
|--------------------------------------------------------------------|
|-----------------------------|
| Buffalo Creek Software |
| Attention: Mike Woltz |
| 913 - 39th Street |
| West Des Moines, Iowa 50265 |
|-----------------------------|
Page 2
-----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
-----------------------------------------------------------------------
Mike Woltz and/or Buffalo Creek Software shall in no way be held
responsible for any damage incurred while operating SPITFIRE. All
responsibility lies with the user of the software.
No part of this manual may be reproduced, transmitted, transcribed,
stored in a retrieval system, or translated into any language (natural
or computer), in any form or by any means, without the prior written
permission of Mike Woltz.
THIS SOFTWARE IS NOT FOR SALE! You are granted a limited license
to use the software described in this manual. The software may be used
or copied only in accordance with the terms set forth herein.
You may not make any changes or modifications to SPITFIRE, and you
may not de-compile, disassemble, or otherwise reverse-engineer it. You
may not rent or lease it to others.
No fee, charge or other compensation may be accepted or requested
by anyone without express written permission from Mike Woltz. This
includes disk vendors.
Operators of electronic bulletin board systems (Sysops) may post
SPITFIRE for downloading by their users without written permission
only as long as the conditions set forth herein are met. A fee may be
charged for access to the BBS as long as no specific fee is charged
for access to the SPITFIRE files.
Distributors of public domain and user supported software, such
as disk vending services, may distribute copies of SPITFIRE subject to
the above conditions only after obtaining written permission from Mike
Woltz.
There are a number of very good bulletin board software packages
available and your selection of SPITFIRE is truly appreciated. Once
again, thank you very much for your support of SPITFIRE.
1.1 - COPYRIGHT & REGISTERED TRADEMARK NOTICE
---------------------------------------------
SPITFIRE and affiliate programs distributed with it are not to be
modified or distributed in modified form without the express written
consent of Mike Woltz.
SPITFIRE is NOT to be sold, used or modified for, or with, illegal
intent under the penalty of law.
"SPITFIRE" is Copyright (C) 1987-1993 by Mike Woltz
"SPITFIRE" is a registered trademark of Buffalo Creek Software.
"Turbo Pascal" is a registered trademark of Borland International Corp.
Page 3
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
"BRK" is Copyright (C) 1985, by Solid Systems
"SEALINK" is Copyright (C) 1986 by System Enhancement Associates
"WILDFIRE" is Copyright (C) 1988-1993 by Stephen L. Cox
"LAKOTA" is Copyright (C) 1992, 1993 by Buffalo Creek Software
"MUV" is Copyright (C) 1989-1993 by Buffalo Creek Software
"KOLDBOOT" is Copyright (C) 1990-1993 by Buffalo Creek Software
"DSZ" is Copyright (C) 1988-1993 by Omen Technology, Inc.
"WINDOWS 3.0" is Copyright (C) 1990-1993 by Microsoft
"DESQview 386" is Copyright (C) 1990-1993 by Quarterdeck Office Systems
"LANtastic" is Copyright (C) 1991-1993 by Artisoft
"Doorway" is Copyright (C) 1987-1993 by Marshall Dudley
"Remdoor" is Copyright (C) 1989-1993 by Ken Brown
"HS Link" is Copyright (C) 1992-1993 by Samuel H. Smith
2.0 - SPITFIRE HARDWARE REQUIREMENTS
------------------------------------
The following are considered the minimum equipment requirements
for running SPITFIRE:
<1> MS-DOS/IBM compatible personal computer
<2> At least 256K memory
<3> Minimum DOS v3.0
<4> Fixed disk (preferable)
<5> Modem
SPITFIRE requires several files being open at the same time.
For this reason, you will need to have the following files and buffers
set in your system's CONFIG.SYS file, located in your root directory.
SPITFIRE may not work properly if this is not done!
CONFIG.SYS should have the following settings:
FILES=25
BUFFERS=30
DEVICE=ANSI.SYS
DEVICE=BRK.DRV
Page 4
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
The "DEVICE=BRK.DRV" is optional, however, if your system supports
the use of SPITFIRE Doors, External File Transfer Protocols, or any
of the Sysop Configurable commands from the Main, File or Message Menus
the use of BRK (or some similar utility) is certainly recommended.
More information regarding the use of BRK is provided in the EXTERNAL
FILE PROTOCOLS section of this manual.
If you are unfamiliar with how CONFIG.SYS works, consult your DOS
manual. If you do not configure your system to allow at least 25 files
to be open at once, you may have a problem with SPITFIRE aborting and
displaying a message of Runtime error 004.
SPITFIRE supports a number of features which cause it to search
the PATH for COMMAND.COM. To work properly, SPITFIRE must be
able to find COMMAND.COM residing in a directory set up in your path
statement. These features are the ability to jump to DOS, the Sysop
configurable features from each menu, execution of the SFINIT.BAT or
the SFMSGPCK.BAT and external file transfer drivers. In the event you
are unfamiliar with setting a PATH, please refer to your DOS manual.
2.1 - MODEMS
------------
SPITFIRE automatically determines your incoming callers' baud
rate. In order for this to work, your modem must be able to send
verbose result codes. Appendix A contains a list of modems and their
corresponding initialization strings which have been reported to work
with SPITFIRE. SPITFIRE determines the baud rate of incoming calls
by receiving the verbose result code from your modem when the modem
establishes carrier detect. Listed below are examples of verbose
result messages returned by most modems.
300 Baud - CONNECT
1200 Baud - CONNECT 1200
2400 Baud - CONNECT 2400
7200 Baud - CONNECT 7200
9600 Baud - CONNECT 9600
14400 Baud - CONNECT 14400
16800 Baud - CONNECT 16800
Error-correction modems
-----------------------
1200 Baud - CONNECT 1200/ARQ
2400 Baud - CONNECT 2400/ARQ
7200 Baud - CONNECT 7200/ARQ
Page 5
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
9600 Baud - CONNECT 9600/ARQ
14400 Baud - CONNECT 14400/ARQ
16800 Baud - CONNECT 16800/ARQ
SPITFIRE's default modem initialization string seems to work with
many modems. Some modems, however, may require a unique initialization
string. There are three modem register settings that MUST exist in
your modem initialization string for SPITFIRE to work properly. They
are S0=0, V1 and S2=1.
There are a number of firms (modem manufacturers, etc) who
graciously provided evaluation products for testing with SPITFIRE.
Mike Woltz and Buffalo Creek Software would like to express much
appreciation to these firms for their help and support. These firms
are not listed for fear that we would omit a name.
2.2 - MODEM INITIALIZATION
--------------------------
When SPITFIRE is booted, it sends the Pre-Initialization string
the Sysop configures at the ALT+M SPITFIRE Async Configuration window,
pauses and then sends the configured modem initialization string to
the modem after each caller. This procedure and SPITFIRE's default
initialization string (listed below) seems to work fine with most
modems:
ATS0=0Q0V1E0M0H0S2=1X1^M
In the event you are using an USR HST and wish to run your BBS
at 19200 baud, the initialization string below works:
ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6^M
In the event you are using a USR HST Dual Standard and wish to
run your BBS at 38400 baud in V.32 mode, the initialization string
listed below works:
ATS0=0B0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X6^M
Should you need to change the modem initialization string, you
select ALT+M at the "SPITFIRE ready for use" prompt. Appendix A
contains a listing of modems and corresponding initialization
strings which have been reported to work with SPITFIRE. The modem
initialization string can also be altered at the DOS prompt by
entering the following command line parameters:
Page 6
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SPITFIRE /M ATS0=0Q0V1E0M0H0S2=1X1^M (Your Initialization String)
Using the same command line parameters, the modem initialization
string can be included within the SF.BAT file. Please note, however,
the command line parameters set in SF.BAT will always override those
set by using ALT+M at the "SPITFIRE ready for use" prompt.
3.0 GETTING STARTED
--------------------
If you're like most computer users, you're probably not thrilled
with the prospect of reading the entire documentation of SPITFIRE. Most
folks are going to boot this program and try to run SPITFIRE without
reading further. So here are some quick guidelines regarding your
initial setup of SPITFIRE.
<1> Create a directory named SF on the drive on which you intend
to run SPITFIRE. Copy all SYSTEM FILES into your newly
created SF directory. (Listed in the SPITFIRE SYSTEM FILES
section of this manual.)
<2> Included in the SPITFIRE package is a file named SF.BAT.
You may need your favorite text editor (as long as it saves
in ASCII format) to modify this file. Examine the default
values (such as target and source drives) and configure them
to comply with your setup. (Example: The default drive
specification is C: and if you're running SPITFIRE on drive
D, then you'll need to change this to D: ). After finishing
that, look for the line that contains SPITFIRE /I2400 /C1.
"/I2400" indicates the top speed of your modem. You may need
to modify this to reflect the highest speed your modem is
capable of. (For example: If you have a 9600 baud modem,
change the string to read "SPITFIRE /I9600 /C1" or "SPITFIRE
/I19200 /C1"). "/C1" indicates the COMM port you are using.
In the event you are using COMM port 2, you need to change
the string to read "SPITFIRE /I2400 /C2". After you've made
these changes, be certain to save your modified file to disk.
**NOTE** The default command line parameters are used for
booting SPITFIRE on your system for the first time. After
setting these parameters in SPITFIRE by using the ALT+M modem
configuration window, any unnecessary command line parameters
(i.e., SPITFIRE /I2400 /C1, etc.) should be removed from your
SF.BAT file.
Page 7
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<3> Now you are ready to boot SPITFIRE by using your SF.BAT
file. When first booting SPITFIRE, you will get the prompt
"SFSYSTEM.DAT not found! Do you wish to create it? <Y/n>".
SPITFIRE defaults to "Y" and by pressing <ENTER> or entering
"Y" for yes, SPITFIRE creates one. Subsequently, SPITFIRE
provides similar prompts for other required files. These
include:
SFNODE.DAT
SFUSERS.DAT
SFFAREA.DAT
SFMCONF.DAT
By pressing <ENTER> or "Y" at each prompt, SPITFIRE will
automatically create the file and place it in the appropriate
directory.
The first thing to be concerned with is not properly
assigning the correct COMM port. In the event you have
the wrong COMM port configured, it is possible that SPITFIRE
will lock up at this point. In such case, refer to step
number 2 in this section. If the COMM Port is properly
assigned, you will then be prompted for the Sysop's Name.
The name you enter here is the name that the callers will
see as Sysop of the system. You should enter your real full
name.
Next, SPITFIRE will ask you for a Sysop Caller Name. It
is recommended you answer this prompt with "Sysop". (The
name you enter here, should be the name that you use to log
on the BBS.) SPITFIRE addresses all comments left for the
Sysop to this configured name.
SPITFIRE will next prompt you to input a password, phone
number, city, state/province and date of birth. SPITFIRE
uses these responses to automatically add you as the first
caller in the SFUSERS.DAT file.
If your modem is malfunctioning, disconnected or turned
off, SPITFIRE will display the message "Your modem is not
responding properly! Do you wish to continue? <y/n>".
Answer "Y" and SPITFIRE will progress to the "SPITFIRE ready
for use..." prompt. Press ALT+M to modify the modem's
initialization string to one which will work properly with
your modem. (Refer to #5 of this section for configuring
SPITFIRE for your modem.)
<4> At the "SPITFIRE ready for use..." prompt, press ALT+S to
log on locally as Sysop. When asked for your name, you must
enter the same name as you entered as the Sysop Caller Name
Page 8
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
when configuring SPITFIRE. (If you use the name "Sysop", the
system will ask for a last name. Simply press <ENTER> and
continue.) Next enter the password you previously selected.
At the Main Menu, press F2 and set your security level to
999. Now move from menu to menu and view the various
features. After viewing and experimenting with the various
features, log off by pressing G for Goodbye and next press
Y to answer Yes to the "Are you sure you want to logoff?"
prompt. SPITFIRE will reset and the "SPITFIRE ready for use"
prompt will appear at this point.
<5> At the "SPITFIRE ready for use..." prompt you may view
or modify your modem configuration by pressing ALT+M.
These keystrokes open SPITFIRE's Modem Configuration window.
The commands that you will see are listed below:
--< SPITFIRE NODE 1 ASYNC CONFIGURATION >--
<S> Serial Port No................... : 1
<B> System Baud Rate................. : 19200
<P> Pre-Initialization String........ : ATZ^M
<I> Initialization String............ :
ATS0=0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X1^M
<M> Modem - Error Correction Type.... : Yes <1> Line COM1.. : IRQ4
<E> Error Correction Message......... : ARQ <2> Line COM2.. : IRQ3
<H> Hardware Data Flow Control....... : Yes <3> Line COM3.. : IRQ4
<A> Answer On What Ring.............. : 1 <4> Line COM4.. : IRQ3
<D> Display Result Messages.......... : On
<C> Disconnect Delay................. : 28
<U> Use High Speed Async Routines.... : Yes
<R> Baud Rate Requirement............ : 1200
<L> Break Length..(1000=1 Second).... : 100
Enter Command or <Q>uit -
Command <S> Specifies the COMM Port being utilized by this node.
Command <B> Defines the maximum baud rate allowed by this node.
The maximum comm port speed in SPITFIRE is 115200.
Command <P> Specified the pre-initialization string sent to the
modem prior to initializing the modem. ATZ^M should
be used in most instances. However, some modems do
not require the carriage return (^M). If this is
the case with your modem, simply use ATZ here.
Page 9
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
*** NOTE *** The caret sign (^) is entered by pressing the shift
key in combination with the numeric 6 key and should
not to be confused with the caret sign which is used
to indicate a control character when creating SPITFIRE
Display Files.
Command <I> Sets the modem initialization string appropriate for
your modem. In most cases, a carriage return, a ^M
should be placed at the end of your initialization
string. However, some modems do not require the
carriage return. If this is the case with your modem,
simply do not include the ^M at the end of your
initialization string.
*** NOTE *** The caret sign (^) is entered by pressing the shift
key in combination with the numeric 6 key and should
not to be confused with the caret sign which is used
to indicate a control character when creating SPITFIRE
Display Files.
Command <M> Specifies whether the modem is an error correction
modem. The modem manual should provide information as
to whether it has error correction capabilities.
Press <M> to toggle this from Yes to No and vice
versa.
Command <E> Specifies the Error Correction Message for your
particular modem if an error correction modem is
being used. For instance, US Robotics uses ARQ.
Please refer to your modem manual to determine the
error correction message used by your modem, provided
it has error checking capabilities.
Some of the newer model modems use different result
codes when an error correction connection is detected.
SPITFIRE is hardcoded to automatically search for
ARQ, MNP and REL result codes which indicate an error
correction connection has been made. In addition to
these, SPITFIRE will search for the error correction
control message the Sysop configures here.
Command <H> Toggle the Hardware Data Flow Control between Yes and
No. For more information on this, refer to the
section - HARDWARE/SOFTWARE DATA FLOW CONTROL - of
this manual.
Command <A> Specifies on what ring SPITFIRE will answer incoming
calls. For instance, with 1, SPITFIRE answers the
incoming call on the first ring. Most often, you will
want this set to 1.
Page 10
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <D> Toggles On or Off SPITFIRE's display of the modem's
verbose message. For instance, when toggled On and a
caller logs on at 2400 baud, CONNECT 2400 is
displayed to the screen and is also recorded in the
CALLERS.LOG. If this is toggled Off, the CONNECT
message will not be written to the screen or recorded
in the CALLERS.LOG.
Command <C> Specifies the disconnect delay. This feature is for
modems utilizing a data buffer. The Sysop may use
this option to configure the amount of time to delay
the disconnect, allowing the data contained in the
modem buffer to be displayed to the caller. SPITFIRE
defaults to 28, which is adequate for the 5k buffer
in the US Robotics HST.
Command <U> This switch should be set to On provided your system
operates properly using high speed routines. If your
display files are not properly shown to the remote
caller, then turn this switch Off.
Command <R> This switch sets the minimum baud rate for access to
your BBS. For instance, if this is set at 1200, a
caller must connect at a baud rate between 1200 and
the maximum baud rate of your BBS. Callers connecting
at baud rates less than that specified here will
be shown SF2SLOW.BBS and the caller will be logged off
the system. This is a variable option and can be set
to disallow callers with a baud rate of 65535 or less.
Command <L> Sets the break length for each tilde found in the
modem initialization string. If the break length is
set at 500, each time SPITFIRE finds a tilde symbol
in the modem initialization string, it will pause for
1/2 second.
Command <1> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 1. IRQ4 is standard for COM1.
Valid options are 1 through 7.
Command <2> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 2. IRQ3 is standard for COM2.
Valid options are 1 through 7.
Command <3> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 3. Valid options are 1 through 7.
Command <4> Allows the Sysop to configure the IRQ SPITFIRE will
use for COMM port 4. Valid options are 1 through 7.
Page 11
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<6> At the "SPITFIRE ready for use" prompt, press ALT+Z.
Pressing ALT+Z opens the window which allows you to
configure SPITFIRE. The commands that you will see
are listed below:
--< SPITFIRE CONFIGURATION >--
<A> Sysop Caller Name............ : Sysop
<B> Sysop Security............... : 50
<C> New Caller Security.......... : 10
<D> New Caller Log On Time....... : 45
<E> No Activity Time Limit....... : 3
<F> Daily Time Limit............. : 60
<G> Log On Time Limit............ : 60
<H> Maximum Callers In Database.. : 500
<I> Maximum Caller Daily Access.. : 10
<J> # Of Callers................. : 1
<K> # Of File Description Lines.. : 2
<L> Upload Time Compensation..... : 1.000
<M> Drop to DOS Password......... : ***********************
<N> BBS Starting Date............ : March 3, 1993
<O> Sysop Name................... : John Doe
<P> Node Number.................. : 2
<R> Private BBS Security Level... : 0
<S> Total Number Of Nodes........ : 3
<T> U/D Ratio Violation Security. : 25
<U> Upload Disk Space Requirement : 100K
ENTER COMMAND [<Q>... Quit]:
Command <A> Use this command to enter or change the Sysop Caller
Name.
Command <B> Sets the Sysop security level. Any caller with an
access equal to or greater than this value can read
all messages (public and non-public), undelete
messages, delete any message, copy a message and
overwrite existing files when uploading (the filename
already exists) as well as being able to perform other
functions not available to callers with a security
level less than what is configured here.
Command <C> Sets the default security level for a new caller.
Command <D> Sets the amount of time a new caller is allowed on the
BBS. (First day only)
Command <E> Sets the amount of time a caller can remain inactive
(no keyboard input) before being automatically logged
off the BBS.
Page 12
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <F> Sets the amount of time per day a caller is allowed on
the board. Refer to the section on SPITFIRE FILE
CLARIFICATION in this manual for more information on
setting daily time limits in SPITFIRE's DAILYLMT.DAT.
Command <G> Sets the amount of time allowed per call for each
caller. Refer to the section on SPITFIRE FILE
CLARIFICATION in this manual for more information on
setting daily time limits in SPITFIRE's DAILYLMT.DAT.
Command <H> Determines the number of callers you will allow to
utilize your BBS. (i.e. - If you have this value set
at 500 and you already have 500 callers and a new
caller (501) tries to log on, the system displays the
file MAXUSERS.BBS and logs the caller off.)
Command <I> This command limits how many times a caller can call
the board each day. If this amount is exceeded, the
system will display TOOMANY.BBS and log the caller
off.
Command <J> This allows the Sysop to set the number of callers.
The reason for this command is if you are already
running an established board, you can enter the
current number of callers, so as not to start the BBS
with Caller Number 1.
Command <K> Sets the number of descriptive lines callers can input
when uploading files to the BBS. Valid options are 1
through 4. If set to 1, only single-line descriptions
are allowed. Using 2, 3, or 4 allows multi-line file
descriptions. If this option is set to allow multi-
line file descriptions and a caller uploads a file for
Sysop Only, the entire multi-line description is
written in the HEYSYSOP.LOG. If the ALT+T option
K, Uploaded By Description, is set to Yes it will
add 1 line to the description crediting the uploader.
So even if this option is set to 1, if the ALT+T
option K is set to Yes multi-line file descriptions
will result.
Command <L> Sets the ratio for the amount of time a caller is
compensated in relation to the amount of time spent
uploading. SPITFIRE defaults to 1.000. If you wish
to reward the caller with additional time for uploads,
increase this numeric value. For instance, if this is
set at 2.000 and a caller spends 10 minutes uploading,
the caller is compensated 20 minutes after the upload
is completed.
Page 13
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <M> Sets the password that is needed to drop to DOS from
a remote location. The default is a blank line. To
use this feature, 'a drop to DOS' password must be
configured. The configured password is disguised by
asterisks and is never visible. Should you forget
the drop to DOS password, it can be reconfigured.
Command <N> This command sets the starting date of your bulletin
board. If you are already running an established
board, you can enter the original starting date of
your BBS rather than the date of your conversion to
SPITFIRE.
Command <O> Allows you to change the Sysop name. This is the name
callers will see credited as the Sysop of the BBS.
Command <P> Sets the Node Number for this particular node of the
BBS. If you are not operating a multi-node system,
this should be set to 1. If you are operating a
multi-node BBS, the node number set should correspond
to the appropriate node number. In other words, the
second node should be set to 2, the third node set to
3, etc. SPITFIRE supports up to 255 nodes.
Command <R> This command sets the security required to access the
BBS if the BBS has been toggled to be a private BBS.
If a caller attempts to log on the BBS and does not
have a security equal to or greater than what the
Sysop has set here, the display file, PRIVATE.BBS/CLR,
if it exists, is displayed and the caller is logged
off the BBS. Those using multi-node systems should
set this for each individual node.
Command <S> Sets the total number of nodes available on your
system. For single node systems, a 1 is entered,
and for multi-node systems, it would be equivalent
to the total number of nodes supported in your system
setup. SPITFIRE supports up to 255 nodes.
Command <T> Specifies the security level that a caller will be
changed to if the upload/download ratio is violated.
SPITFIRE's DAILYLMT.DAT file defines parameters for
determining if and when a caller's security is
adjusted for violating the upload/download ratio. The
DAILYLMT.DAT file must define a VWR (Violation Warning
Ratio) and a VER (Violation Enforcement Ratio). The
VWR and VER should be defined for each security level
on the BBS for which the Sysop desires to monitor
Page 14
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
upload/download requirements. (Refer to the section -
SPITFIRE FILE CLARIFICATIONS - for further information
on SPITFIRE's DAILYLMT.DAT.)
If SPITFIRE finds the VWR and VER is defined for the
security level of the caller, each time a file is
downloaded, SPITFIRE performs the following
calculations to determine if a caller has violated
the upload/download ratio requirement:
The number of files downloaded by a caller is divided
by the number of files uploaded AND the number of
kilobytes downloaded by the caller is divided by the
number of kilobytes uploaded by the caller. SPITFIRE
must verify that both the file ratio and the kilobyte
ratio have been violated. If the results of both the
file and kilobyte calculation are greater than the
value defined for the VER (Violation Enforcement
Ratio), SPITFIRE will then alter the caller's security
level to that configured here at the U/D Ratio
Violation Security.
**NOTE** SPITFIRE will return the caller to their original
security once the caller's upload/download ratio is
again within the required ratio limits. SPITFIRE's
SFUSERS.DAT file contains a field which stores
information regarding the caller's original security
level. When a caller uploads a file to the BBS,
SPITFIRE first checks to see if the caller's current
security level is less than their original security.
If so, SPITFIRE performs the same computations as
described above. If the results of the file or
kilobyte calculation is less than the VER (Violation
Enforcement Ratio), the caller's original security
level is restored.
Command <U> Allows the Sysop to configure the amount of disk
space which must be available on the upload drive
before a caller will be allowed to perform an upload.
The default is 100K.
After completing your configuration for SPITFIRE enter <Q> to Quit
and the "Ready..." prompt is displayed.
<7> Pressing ALT+T (from the SPITFIRE ready prompt) allows you
to configure the SPITFIRE toggle switches. A window opens
up to display the following configuration options:
Page 15
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
-----< Toggle SPITFIRE Switches >-----
<A> US Phone Number Style......... : On
<B> Log On - Message Statistics... : On
<C> Log On - New File Statistics.. : On
<D> Require New Caller Birthdate.. : Yes
<E> New Caller Default Protocol... : Yes
<F> File Description Conversion... : On
<G> Type Of BBS................... : Public BBS
<H> Graphics...................... : Ansi Available
<I> Second Password............... : One Password
<J> Direct Screen Writes.......... : Yes
<K> Uploaded By Description....... : Yes
<L> Password Failure Comment...... : No
<M> Require Door Return Password.. : No
<N> Scan All Msg Conferences...... : Yes
<O> Comprehensive Upload Search... : On
<P> Color Monitor................. : Yes
<R> Test Files Upon Boot.......... : Yes
<S> Search CD Rom Area SFFILES.... : No
Enter Command <<Q>... Quit>:
Command <A> This allows the Sysop to set whether the BBS will
use the US phone number format (###-###-####) or
allow SPITFIRE to accept any 12 character string
entered by the caller. SPITFIRE defaults to the US
Phone Number Style set to On.
Command <B> This feature enables the Sysop to determine whether
callers will be prompted with their message statistics
when logging on the BBS. If this is set On, the
caller is notified upon log on of any new messages,
number of received messages, messages sent by the
caller and total number of messages on the BBS.
SPITFIRE's default is On.
Command <C> Allows the Sysop to designate whether callers are
prompted with new file statistics when logging on. If
this is set to On and the caller opts to view new
files, a list of all new files will be displayed to
the caller. Additionally, SPITFIRE informs callers of
the number of new files since last checked and the
total downloadable files and bytes available on the
system. SPITFIRE's default is On. SPITFIRE will not
check for new files or report file statistics on a
file area that is configured as a CD-ROM file area.
Page 16
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <D> Designates whether a new caller logging onto the
BBS for the first time is required to enter their
date of birth. If toggled to Yes, the birthdate is
required. If toggled to No, the caller is not
prompted to enter their date of birth.
If Command <I>, Second Password, is toggled to
Second Password Required, and the Require New Caller
Birthdate is changed to No, SPITFIRE will
automatically change Command <I> to One Password.
**NOTE** SPITFIRE uses a caller's date of birth as the second
password, when required. It is impossible to
require a second password if the BBS does not
require the caller to enter their date of birth.
Command <E> This feature determines if a new caller logging on
the BBS can select a default file transfer protocol
after completing the new caller questionnaire. If
this is toggled to Yes, the new caller is presented
this option. If this feature is set Off, the new
caller is not automatically presented with this
option, but may still select a default file transfer
protocol from the <Y>...Your Statistics option of the
Main Menu.
Command <F> Toggles SPITFIRE's File Description Conversion On
and Off. When toggled On, SPITFIRE automatically
converts the first character of each word in the
file description to uppercase. All other characters
will be lower case. The exception to this is any
words the Sysop includes in SFUPCASE.DAT (in the
Work File Path). These words are converted to all
uppercase characters, i.e., BBS, SPITFIRE, COMM, ZIP,
etc. If toggled Off, SPITFIRE makes no attempt to
alter the description entered by the caller.
SPITFIRE's default is On.
Command <G> Toggles the BBS to a Private or Public system. If you
toggle this as a Private BBS, then the caller's name
must be found in the callers file and the caller's
security must be equal to or greater than that
configured for option <R> Private BBS Security Level
at the ALT+Z configuration screen prior to being
granted access. If you have the system toggled as a
Private BBS and a caller tries to log on as new caller,
then SPITFIRE displays NEWUSER.BBS/CLR (if found) and
has the new caller answer the new caller questionnaire
(if found). After the questionnaire is answered,
Page 17
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SPITFIRE displays PRIVATE.BBS/CLR (if found) and logs
the caller off. A note is left in HEYSYSOP.LOG to
advise the Sysop that a new caller attempted to log on.
Command <H> Toggles ANSI graphics On or Off. If you wish to offer
ANSI graphics, you must create .CLR files to match the
display .BBS files you have, (i.e., ALL.BBS {non-ANSI}
& ALL.CLR {ANSI Graphics}). In order for you to see
the ANSI Graphics locally, DEVICE=ANSI.SYS must exist
in your CONFIG.SYS file.
Command <I> Toggles password prompt. If toggled to One Password,
the caller simply enters their password. If toggled
to Second Password Required, after entering the
first password, the system prompts the caller for
their birth date. Should the caller not know their
birth date, the system logs them off.
**NOTE** If the BBS is configured not to require a caller to
enter their date of birth when logging on to the BBS
the first time, SPITFIRE automatically sets this
option to One Password, if it is not already. The
Second Password Required is only available when
callers are required to enter their birth date.
Command <J> Toggles the Direct Screen Write feature on and off.
If you are running SPITFIRE in a multi-tasking
environment, you will want to set this to No to
disable direct screen writing. Otherwise, set this
to Yes because using direct screen writes increases
the speed of the display.
Command <K> Toggles whether a line is added to the file
description crediting the caller who uploaded the
file. The line, "Uploaded By <Caller's Name>" will
appear on the last line of the file description if
this is set to Yes. If set to No, the file
description appears as entered by the caller with
no information referencing the uploader.
Command <L> Toggles whether a caller who is unable to enter
their password may leave a Comment To The Sysop. If
toggled to "No", the caller is not prompted for a
comment. When toggled to "Yes", the caller is given
the option of leaving a comment to the Sysop before
being logged off the BBS.
Command <M> Toggles whether the BBS requires a caller to enter
their passwords when returning to SPITFIRE from the
door section of the BBS. If toggled to No, entering
their password is not required.
Page 18
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <N> This feature allows Sysops to designate the message
scan parameters. When set to Yes, all message
conferences are included in the scan. When set to No,
only messages in the caller's queued conferences are
scanned. This affects both the log on message scan
and the scan performed when selecting <Y>...Your
Message option from the Message Menu.
Command <O> This feature provides Sysops the option of configuring
whether the system will take advantage of SPITFIRE's
comprehensive file search when callers attempt an
upload. If toggled Off, SPITFIRE searches for exact
matches. If a match is found, the callers are
informed that the file already exists on the BBS.
When toggled On, SPITFIRE trims any trailing digits
from the file name during the search, replacing the
numeric values with the '*' wildcard. For instance,
if a caller attempted to upload SF33.ZIP, SPITFIRE
would then search for SF*.ZIP. SPITFIRE would report
individually all SF*.ZIP files it found on the BBS
and prompt the caller as to whether they still wish
to continue with the upload.
**NOTE** The Comprehensive Upload Search does not prevent
callers from uploading the file. This feature is meant
only to make the callers aware that another version of
this file already exists on the BBS. Hopefully the
majority of callers are responsible enough not to
upload older versions of existing files, but rather
only the more current, updated versions.
Command <P> This feature allows the Sysop to toggle whether or
not the monitor used for the BBS is a color monitor.
Command <R> Toggles whether SPITFIRE tests the various message
base files to assure that the files are in working
condition. If toggled On, when SPITFIRE is booted
the message base files are tested. If toggled Off,
no tests are performed. Sysops with numerous message
conferences may wish to toggle this Off to speed
the boot process. SPITFIRE defaults to On and this
setting is recommended to ensure file integrity.
Command <S> Toggles whether a File Area configured as a CD-Rom
Area (refer to the section, Configuring File Area
Records) will search SFFILES.<x> during file searches
rather than the CD-Rom drive. This option allows the
Sysop the opportunity to configure SPITFIRE to work
with a CD-Rom in the most efficient manner. If it is
Page 19
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
faster to search the CD-Rom drive, then toggle this
option to No. However, if it is faster to search the
SFFILES.<x>, then toggle this option to Yes.
<8> When setting up a SPITFIRE BBS for the first time, SPITFIRE
automatically creates the default file paths:
--<SPITFIRE FILE PATHS>--
<A> Work Files Path..................: C:\SF\WORK
<B> Message Files Path...............: C:\SF\MESSAGE
<C> Display Files Path...............: C:\SF\DISPLAY
<D> External Transfer Path...........: C:\SF\EXTNOD1
ENTER COMMAND < <Q>...Quit> :
SPITFIRE also places any files it creates in the appropriate
file path.
If you wish to modify these settings, you may do so by
pressing ALT+P at the "Ready..." prompt. Pressing ALT+P
opens the window which allows you to set the file paths
used when running SPITFIRE. An explanation of the commands
are listed below:
Command <A> Specifies the directory in which the SPITFIRE Work
Files reside. (For more information on this refer
to the section FILE PATHS in this manual.) All files
belonging in the Work File Path are specified as such
with a (WORK) in the file description in the section -
SPITFIRE WORK FILES.
Command <B> Allows you to specify the directory in which the
SPITFIRE Message Files will reside. All files
belonging in the Message File Path are specified
as such with a (MESSAGE) in the file description in
the section - SPITFIRE MESSAGE FILES.
Command <C> Specifies the directory in which the SPITFIRE Display
Files reside. All files with a BBS or CLR extension
are Display Files and should reside in the directory
you designate here. (For more information refer to
the section on FILE PATHS in this manual.) All files
belonging in the Display File Path are specified as
such with a (DISPLAY) in the file description in the
section - SPITFIRE DISPLAY FILES.
Command <D> Allows you to specify the directory from which you
opt to run the SPITFIRE External Transfer Protocols.
Page 20
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
All files which you are using to run the External
Transfer Protocols must reside in the directory you
designate here. (For more information refer to the
section - EXTERNAL FILE TRANSFER PROTOCOLS of this
manual.)
Establishing specified file paths provides Sysops with more
manageable directories. However, if the Sysop prefers, all files can
be accessed from the SF directory. Simply enter C:\SF in response to
each of the above file path questions.
After you've configured SPITFIRE to meet your specifications,
Quit and return to the "SPITFIRE ready for use..." prompt.
At the "SPITFIRE ready for use..." prompt, press ALT+R to
configure your Message Conference records and ALT+F to configure your
File Area records. For more information on this feature, refer to the
section - SETTING UP SYSTEM RECORDS of this manual.
After you've completed that, you're ready to go!
If you encounter problems running SPITFIRE, and you're sure you've
tried everything, gather together a report of your version number along
with information pertaining to the difficulties you are experiencing
(such as System, Modem, Comm Port) and contact Buffalo Creek's BBS at
(515-225-8496) for support. Be as thorough as possible so an accurate
determination of the cause of your problem(s) can be made. Every
effort will be made to determine and correct the problem! Please keep
in mind that it is difficult at best to provide help if you simply
leave a message that says something like, "I can't make external
protocols work. What am I doing wrong?". You need to provide specific
information regarding the problem.
Furthermore, if you've had a problem which isn't covered by this
manual and were able to work it out without support, please contact
Buffalo Creek's BBS so the information you have discovered can be
shared with other users of SPITFIRE. Also, please report any unique
configurations you may discover so everyone will benefit from your
ideas.
4.0 SPITFIRE FILE PATHS
-----------------------
SPITFIRE supports paths for the files which are accessed in the
process of its execution. Using the individual file paths created
by SPITFIRE (SYSTEM, WORK, MESSAGE, DISPLAY and EXTERNAL), your
directories are more manageable.
Page 21
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
The SYSTEM files path is the directory in which you have set up
SPITFIRE (usually C:\SF) and contains files required for the execution
of SPITFIRE. The WORK files path contains files which SPITFIRE
accesses and writes to periodically in the process of program
execution. The DISPLAY files path contains all files which are
displayed to the caller while logged on the BBS. The MESSAGE files
path contains all files used by the message section of SPITFIRE. The
EXTERNAL files path includes the files necessary to provide the caller
with optional transfer protocols other than those provided in SPITFIRE.
**NOTE** All DISPLAY files are optional. Should the Sysop choose
not to use these files, SPITFIRE will operate just fine. In fact,
SPITFIRE will normally display a default message when a display
file is not found. The DISPLAY files merely provide an additional
means by which the Sysop can create unique screens to personalize
their BBS system.
The system files that were created when setting up SPITFIRE
MUST reside in the main SPITFIRE directory. The WORK, MESSAGE,
DISPLAY and EXTERNAL file paths are created by SPITFIRE or can be
modified by pressing ALT+P at the "SPITFIRE Ready For Use" prompt.
(Refer to the section - GETTING STARTED of the SPITFIRE manual.)
The following sections discuss, individually, files used by
SPITFIRE. After the file description, a (SYSTEM), (WORK), (MESSAGE)
or (DISPLAY) is included to help you determine in which directory the
file should be placed. No files which will be used in your External
Protocol Path will be found. These are not included in the SPITFIRE
package because these are separate programs written by other
programmers.
4.1 - SPITFIRE SYSTEM FILES
---------------------------
There are five file types that comprise SPITFIRE and allow it
to function - System, Work, Message, Display and External Protocol.
The first is SYSTEM FILES. System Files are mandatory for
SPITFIRE's operation and MUST reside in your main (also referred to
as HOME) SPITFIRE directory from which you run SPITFIRE.
SPITFIRE.EXE - Main System Program. (SYSTEM)
SPITFIRE.OVR - SPITFIRE Overlay File. (SYSTEM)
SFMAIN.MNU - SPITFIRE Main Menu. (SYSTEM)
SFMSG.MNU - SPITFIRE Message Menu. (SYSTEM)
SFFILE.MNU - SPITFIRE File Menu. (SYSTEM)
SFSYSOP.MNU - SPITFIRE Sysop Menu. (SYSTEM)
Page 22
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
The above-mentioned files MUST be present for SPITFIRE to run.
SPITFIRE will halt if these files are not found in the directory from
which you are running your system.
The following system files will be created by SPITFIRE if they
are not already present.
SFNODE.DAT - Configuration information for this node. (SYSTEM)
SFFAREA.DAT - File Area system information. (SYSTEM)
SFMCONF.DAT - Message Conference system information. (SYSTEM)
SFEVENTS.DAT - Stores information regarding scheduled events.(SYSTEM)
Other system files which will need to reside in the main
SPITFIRE directory include:
SFREMOTE.BAT - Used for remote Drop to DOS. (SYSTEM)
SF.BAT - Batch file for invoking SPITFIRE. (SYSTEM)
SFMAIN.BAT - Executes Sysop configurable command option
available from the Main Menu. (SYSTEM)
SFMAIN.DAT - File created that contains caller information.
SPITFIRE creates this file when a caller uses
the Main Menu Sysop Configurable Command to
execute a third party program. This file is
automatically erased when the caller returns
to SPITFIRE. (SYSTEM)
SFMESS.BAT - Executes Sysop configurable command option
available from the Message Menu. (SYSTEM)
SFMESS.DAT - File created that contains caller information.
SPITFIRE creates this file when a caller uses
the Message Menu Sysop Configurable Command to
execute a third party program. This file is
automatically erased when the caller returns
to SPITFIRE. (SYSTEM)
SFFILE.BAT - Executes Sysop configurable command option
available from the File Menu. (SYSTEM)
SFFILE.DAT - File created that contains caller information.
SPITFIRE creates this file when a caller uses
the File Menu Sysop Configurable Command to
execute a third party program. This file is
automatically erased when the caller returns
to SPITFIRE. (SYSTEM)
SFDOOR.MNU - SPITFIRE Door Menu. (SYSTEM)
SFDOORS.DAT - File created that contains caller information.
SPITFIRE creates this when a caller uses the
SPITFIRE door feature and erases it when the
caller returns to SPITFIRE. (SYSTEM)
DOOR.SYS - Universal door file that contains caller information.
SPITFIRE creates this when a caller uses the
SPITFIRE door feature. (SYSTEM)
Page 23
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFORDER.MNU - SPITFIRE Questionnaire Menu. (SYSTEM)
SFCHAT.CAP - Text file of chat captures. (SYSTEM)
CALLERS.TMP - Temporary file for recording callers activity.
This file is later appended to CALLERS.LOG file
in the WORK file path and erased. (SYSTEM)
DAILYLMT.DAT - Determines daily time limits, number of downloadable
files and bytes, quick log on capability, number of
node chats, etc. for each security level (SYSTEM)
SFINIT.BAT - Batch file, if found, is executed after the caller
logs off and prior to initializing the modem. (SYSTEM)
SFLOGON.BAT - Batch file, if found, is executed when a caller logs
onto the BBS and after the system information is
displayed. (SYSTEM)
SFSEC<X>.BAT - Batch file, if found, is executed after a caller
logs onto the BBS and whose security is equal to
<X> of the SFSEC<X>. (SYSTEM)
BADINIT.BAT - Batch file executed when modem initialization fails,
i.e., SPITFIRE reports the modem is not responding
properly. (SYSTEM)
SPITFIRE.HLP - Help with all commands for all menus. This file can be
modified via SFHELP. Consult the documentation
accompanying SFHELP. NOTE: Systems using the
Sysop configurable command option(s) will need to
modify this help file with SFHELP to include an
explanation of the added feature(s). (SYSTEM)
SFPROTCO.HLP - Extra help with Uploads/Downloads. This is a simple
text file that you can modify with your favorite text
editor, provided it saves in ASCII format. (SYSTEM)
LAKOTA.COM - SPITFIRE companion utility which allows messages
to be downloaded and uploaded in QWK format. (SYSTEM)
SFPCKMSG.COM - SPITFIRE companion utility which purges old
messages from the message base. SPITFIRE shells to
SFPCKMSG.COM when packing messages, either as Event M
or from the Sysop Menu. (SYSTEM)
SFPCKUSR.COM - SPITFIRE companion utility that purges callers
from SPITFIRE's caller database, SFUSERS.DAT. (SYSTEM)
The SFREMOTE.BAT, SFPROTCO.HLP, SFDOOR.MNU, SFORDER.MNU, SF.BAT,
DAILYLMT.DAT, SPITFIRE.HLP, SFINIT.BAT, SFSEC<X>.BAT, SFLOGON.BAT,
SFMESS.BAT, SFMAIN.BAT, SFFILE.BAT and BADINIT.BAT may be edited to
your own personal tastes.
*NOTE* Any Sysop operating a multi-node system must have a copy of
all the system files being used by a particular node in that
node's main SPITFIRE directory. While some files such as
SPITFIRE.EXE are mandatory, other files, such as SFINIT.BAT,
may be optional.
Page 24
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
4.2 SPITFIRE MESSAGE FILES
--------------------------
All files relating to the message conference reside in the MESSAGE
file path. SPITFIRE supports up to 512 message conferences and for
each message conference on the system a SFMSG<X>.DAT, SFMSG<X>.PTR,
SFMSG<X>.LMR and SFMSG<X>.IDX file is created. (<X> refers to the
number of the corresponding message conference and will range from
1 to 512.)
SFMSG<x>.DAT - All messages are contained here. (MESSAGE)
SFMSG<x>.PTR - Message pointers for scans, etc. (MESSAGE)
SFMSG<x>.IDX - Message index file. (MESSAGE)
SFMSG<x>.LMR - Last message read pointer file. (MESSAGE)
* NOTE * Any Sysop operating a multi-node system should be aware that
SPITFIRE allows all nodes to share a common MESSAGE file
path.
4.3 SPITFIRE WORK FILES
------------------------
The third file type is WORK FILES. Although not all of these
files are required to run SPITFIRE, you will, no doubt, find them
invaluable in the operation of your BBS system. These files are
accessed routinely and are periodically written to during the course
of SPITFIRE's execution. If the REQUIRED work files are not found,
SPITFIRE will create them, with the exception of SFCALLOG.DAT. The
SFCALLOG.DAT is not created, but included in the SPITFIRE distribution
package and must be copied over to the directory configured as the
WORK FILE PATH. (SFNEWU.QUE, SFORDER<x>.QUE, SFUPCASE.DAT, SFNOUP.DAT
and SFMSGPCK.BAT are not required and must be created by the Sysop.
SFSYSTEM.DAT - Starting date, number of callers, etc. (WORK)
SFUSERS.DAT - Caller data file. (WORK)
SFUSERS.PTR - Caller data pointer file. (WORK)
SFUSERS.LST - Text file created when caller's data file is
printed to disk from the Sysop Menu (WORK)
CALLERS.LOG - Record of the callers' activities. (WORK)
SFCALLOG.DAT - Stores information used to write caller's log.(WORK)
HEYSYSOP.LOG - Record of special Sysop notification. (WORK)
SFNEWU.QUE - New caller questionnaire. (WORK)
SFNEWU.REP - Contains new caller questionnaire replies. (WORK)
SFORDER<x>.QUE - Questionnaires/Order Forms available to callers
from the Main Menu. (WORK)
SFORDER<x>.REP - Contains callers' responses to the Main Menu
Questionnaires/Order Forms. (WORK)
JOKER.DAT - List of undesirable caller names. (WORK)
Page 25
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFBBSLST.DAT - Contains list of other boards to call. (WORK)
SFUPCASE.DAT - Keywords in a file description that will
be converted to uppercase. (WORK)
SFNOUP.DAT - Files the Sysop does not want uploaded. (WORK)
SFMSG.TXT - A text file that can be imported when entering
or replying to messages if logged on locally. (WORK)
SFMSGPCK.BAT - Batch file, if found, is executed immediately
after packing the message base. (WORK)
SFPURGED.USR - List of callers purged from the BBS. Contains
caller's name, address and security level at the
time of the purge. (WORK)
SFWHOSON.DAT - Information regarding who is logged onto
each node. (WORK)
BBSNAME.DAT - Net-mail tag line data. (WORK)
** NOTE ** Any Sysop operating a multi-node system should be aware that
SPITFIRE allows all nodes to share a common WORK file path.
4.4 SPITFIRE DISPLAY FILES
--------------------------
SPITFIRE uses the following files as display files. If these
are not found, SPITFIRE will run just the same. Display files can
be created using your favorite text editor or screen generating
program.
<x>.BBS/CLR - Displays to caller at log on if the caller
record number equals <x>. (DISPLAY)
<x>SEC.BBS/CLR - Displays to all callers with a security level
equal to <x>. (DISPLAY)
ALL.BBS/CLR - Displays to all callers upon log on, unless
their security allows for a quick log on.(DISPLAY)
BULLETIN.BBS/CLR - Lists the bulletins available to the caller.
(DISPLAY)
BULLET<x>.BBS/CLR - This file displays to callers when <x> bulletin
is selected. <x> can equal 1 to 99. (DISPLAY)
CHATDONE.BBS/CLR - Displays to callers after completing a chat
with the Sysop. (DISPLAY)
DLMT.BBS/CLR - Displays to callers when downloads exceed the
daily limit. (DISPLAY)
DORBUL<x>.BBS/CLR - This file displays to callers when <x> bulletin
is selected from the Door Bulletin Menu, where
<x> can equal 1 to 99. (DISPLAY)
EVENTIME.BBS/CLR - Displays to a caller who logs on and has their
log on-time adjusted so an on-time event can
be completed at a specified time. (DISPLAY)
FILE<x>.BBS/CLR - Non-ANSI and ANSI created file menus that display
to callers whose security level is equal to <x>.
(DISPLAY)
Page 26
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
FILST<x>.BBS/CLR - Listing of available File Areas that displays
to callers whose security level is equal to <x>.
(DISPLAY)
GOODBYE.BBS/CLR - Displays to callers when logging off the BBS.
(DISPLAY)
LOCKOUT.BBS/CLR - Displays to a callers marked as locked out
or is found in JOKER.DAT. (DISPLAY)
MAIN<x>.BBS/CLR - Non-ANSI and ANSI created main menus for each of
the corresponding security levels available
on the BBS. (DISPLAY)
MAXUSERS.BBS/CLR - Displays to new callers when the maximum number
of callers have been reached. (DISPLAY)
MSG<x>.BBS/CLR - Non-ANSI and ANSI created message menus for each
of the corresponding security levels on the BBS.
(DISPLAY)
MGLST<x>.BBS/CLR - Listing of available Message Conferences that
displays to callers whose security level is
equal to <x>. (DISPLAY)
NEEDSYS.BBS/CLR - Displays to callers prior to the connection
being terminated using the ALT+F1 key. (DISPLAY)
NEWUSER.BBS/CLR - Displays to new callers (normally rules of
the BBS). (DISPLAY)
NOSPACE.BBS/CLR - Displays to a caller attempting to upload when
the disk space available is less than what the
Sysop has configured at the ALT+Z Upload Disk
Space Requirement option. (DISPLAY)
PRIVATE.BBS/CLR - Contains message displayed to new callers when
logging on a private system, after answering the
new caller questionnaire (if found). (DISPLAY)
SF1STM.BBS/CLR - Displays to the caller when entering the Message
Section the first time per log on. (DISPLAY)
SF1STF.BBS/CLR - Displays to the caller when entering the file
section the first time per log on. (DISPLAY)
SF2SLOW.BBS - Displays to a caller who connects at a baud rate
lower than what the Sysop has configured as the
minimum baud rate allowed on the BBS. (DISPLAY)
SFASLEEP.BBS/CLR - Displays to a caller who has not entered a
keystroke for the amount of time configured by
the Sysop at ALT+Z's No Activity Time Limit,
prior to logging them off the BBS. (DISPLAY)
SFBATCHD.BBS/CLR - Non-ANSI and ANSI created menus for the
Batch Download Menu. (DISPLAY)
SFBATCHU.BBS/CLR - Non-ANSI and ANSI created menus for the
Batch Upload Menu. (DISPLAY)
SFBDAY.BBS/CLR - Displays to a caller on their birthday. (DISPLAY)
SFDOOR<x>.BBS/CLR - Displays to callers entering the corresponding
SPITFIRE Door program. <x> can be an alphabetical
character A through Z, with the exception of G and
Q which are reserved for use by SPITFIRE.(DISPLAY)
Page 27
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFDORBAK.BBS/CLR - Displays to a caller upon returning to SPITFIRE
BBS after completing a door program if the Sysop
has configured the BBS to require a password
when returning from a door. Normally prompts
the caller for his/her password. (DISPLAY)
SFDORBUL.BBS/CLR - Lists the door bulletins available to the caller
from the SPITFIRE Door Menu. (DISPLAY)
SFDOWN.BBS/CLR - Displays to callers prior to a download. (DISPLAY)
SFDR<x>.BBS/CLR - Non-ANSI and ANSI created door menus for each of
the corresponding security levels on the BBS.
(DISPLAY)
SFEXTDN.BBS - Contains a list of external download file transfer
protocols available on the BBS. (DISPLAY)
SFEXTUP.BBS - Contains a list of external upload file transfer
protocols available on the BBS. (DISPLAY)
SFFILES.BBS - Display file containing the names of files
available for downloading in each of the file
areas on the BBS. This is the only exception to
the rule of placing a Display File in the Display
File Path. An SFFILES.BBS should be placed in
each download directory, listing the files
available for download from that particular file
area. (DOWNLOAD DIRECTORIES)
SFFILES.<x> - Listing of files available for download from a
CD Rom file area. <x> represents the number of
the file area. (DISPLAY)
SFFILE<x>.BBS/CLR - Displays to callers when selecting a specific
file area. <x> would correspond to the area
selected. (DISPLAY)
SFIMPEXP.BBS/CLR - ANSI and non-ANSI menus displayed when logging on
locally and selecting either the <D>..Download or
<U>..Upload option from the File Menu. (DISPLAY)
SFMAINT.BBS/CLR - Displays to the caller after WELCOME1.BBS/CLR
and prior to the caller entering their name if
system maintenance is being performed. After
SFMAINT.BBS/CLR is displayed, the caller is
logged off the BBS. (DISPLAY)
SFMSG<x>.BBS/CLR - Displays to callers when selecting a specific
message conference. <x> would correspond to
the conference selected. (DISPLAY)
SFMQDONE.BBS/CLR - Displays to a caller attempting to answer a
main questionnaire/order form a second time when
it is configured to limit callers to one response.
(DISPLAY)
SFNOD<x>.BBS/CLR - Displays to callers after the ALL.BBS/CLR
and prior to the <X>SEC.BBS/CLR. <x> would
correspond to the BBS node number. (DISPLAY)
SFNOTIME.BBS/CLR - Displays to callers who attempt to log on after
using their daily allotted time. (DISPLAY)
Page 28
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFNWSLTR.BBS/CLR - Sysop's newsletter available from the Main Menu.
(DISPLAY)
SFONFAIL.BBS/CLR - Displayed to a caller who logs on the BBS and
fails to enter the correct password. This could
be used to inform the caller that someone with the
same name already accesses the BBS and they should
attempt to log on using a nickname or their middle
initial. (DISPLAY)
SFORD<x>.BBS/CLR - Questionnaire/Order Form Menu displayed to caller
with a corresponding <x> security level. (DISPLAY)
SFPAGED.BBS/CLR - Displays if the Sysop has the page on and a
caller attempts to page the Sysop again when the
Sysop has not answerd the first page. (DISPLAY)
SFPGOFF.BBS/CLR - Displays to callers paging the Sysop when the
Sysop has the page feature turned off. (DISPLAY)
SFPRELOG.BBS - The first file displayed upon log on. (DISPLAY)
SFPROMSG.BBS/CLR - Displays to the caller prior to selecting a
default file transfer. Sysops should use this
display file to inform callers that if a default
transfer protocol is selected, External Transfer
Protocols will not be available to them. (DISPLAY)
SFRATIO.BBS/CLR - Displays to callers after a download if their
download/upload ratio exceeds your setting and
a VWR (Violation Warning Ratio) exists for the
caller's security level in DAILYLMT.DAT. (DISPLAY)
SFREMIND.BBS/CLR - Displays to callers upon log on if the caller
was logged off during the previous session due
to inactivity. (DISPLAY)
SFTIMEUP.BBS/CLR - Displays to a caller whose log on-time has
expired. (DISPLAY)
SFUNANS.BBS/CLR - Displays to a caller when the Sysop has the
page turned on and the Sysop does not answer
the page. If SFPAGED.BBS/CLR is found in the
display file directory, SPITFIRE will not allow
additional pages if the first page remains
unanswered. (DISPLAY)
SFUP.BBS/CLR - Displays to callers prior to an upload. (DISPLAY)
SOP<x>.BBS/CLR - Non-ANSI and ANSI file created Sysop menus for the
specified security levels. <x> would correspond
to the caller's security level. (DISPLAY)
TOOMANY.BBS/CLR - Displays to callers who exceeds the daily limit
of calls. (DISPLAY)
SYSINIT.BBS/CLR - Displays to the caller upon entering chat if the
Sysop initiated the chat. (DISPLAY)
THOUGHTS.BBS - Contains thoughts created for SPITFIRE with
THOUGHTS.EXE. (DISPLAY)
USERINIT.BBS/CLR - Displays to caller upon entering chat with the
Sysop if the caller paged the Sysop and requested
the chat. (DISPLAY)
Page 29
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
WELCOME1.BBS/CLR - The second file displayed upon log on. (DISPLAY)
WELCOME<x>.BBS/CLR - WELCOME2.BBS/CLR through WELCOME9.BBS/CLR
are displayed in numerical order after a caller
enters the name and password and gains access
to the BBS. (DISPLAY)
* NOTE * Any Sysop operating a multi-node system should be aware that
SPITFIRE will allow all nodes to share a common DISPLAY file
path.
SPITFIRE supports the use of ANSI/Graphics display files. The
ANSI files use the file extension .CLR (color). In the event ANSI
Graphics are available and SPITFIRE does not find the appropriate .CLR
file to display, then the appropriate .BBS file will be displayed. If
neither file is found, SPITFIRE will, in most cases, display a default
message.
IMPORTANT: In the event, ANSI/Graphics are available be sure to
load the ANSI driver (DEVICE=ANSI.SYS) from within your CONFIG.SYS.
NOTE: When making ANSI graphics available to callers, duplicate
all display <filename>.BBS files to ANSI files and call them
<filename>.CLR. For an attractive BBS, offer both sets of files.
The following list of files are an EXCEPTION to this .CLR rule:
THOUGHTS.BBS SFEXTDN .BBS SFEXTUP .BBS
SFFILES .BBS SFPRELOG.BBS SF2SLOW .BBS
SPITFIRE automatically displays SFFILES.BBS in color if the
caller selected ANSI color graphics when logging on the BBS. In the
event a file line is not colored like the others, but rather uses
the caller's default color, it is because the comma in the file size
is either not located properly or does not exist. SPITFIRE utilizes
the comma in the file size to determine the coloring of the SFFILES.BBS
listings.
4.5 SPITFIRE MENU FILES
------------------------
Menu files contain all the information needed for SPITFIRE to
dynamically build each caller's menus, dependent on the caller's
security level.
SPITFIRE displays a feature only if a caller's security level is
high enough to access it. Therefore, callers don't necessarily see
every possible choice in a given menu. This places you in control and
allows you to tailor your board for your individual needs.
Page 30
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
The format used for the SFMAIN.MNU, SFSYSOP.MNU, SFMSG.MNU and
SFFILE.MNU is:
Command Character,Command Description,,Security Level,Command Identifier
Knowing this, let's use the following example:
B,<B>.... Bulletins,,5,A
------------------------
The "B" is the Command Character. This is the letter the
caller must type to access this particular option. In
this instance "B" is used to select Bulletins.
"<B>.... Bulletins" is the Command Description and represents
how the file entry appears in the menu on the screen.
"5" is the minimum Security Level required for the caller to
access this function...or even see it!
"A" is the SPITFIRE Command Character Identifier and should
NEVER be changed. The Command Character Identifier is
constant in SPITFIRE programming. This character is
DIFFERENT for every command.
After exploring a bit, you'll find that SPITFIRE allows you to
design your menus to suit your own personal taste as well as control
what commands are available to what callers. The SFFILE.MNU file that
comes with the SPITFIRE package sets the <D>.... Download A File
security at 10. While a caller is on-line, hit F2 to change the
caller's security to 9 and the Download feature is no longer available
for that caller.
THERE ARE THREE RULES CONCERNING MENU LINES!
--------------------------------------------
You CANNOT change the Command Character Identifier from what it
is in the original distribution package menu!
You CANNOT assign the same Command Letter to two commands in the
same menu!
You CANNOT make the total length of the line more than 40
characters long!
Therefore, if you wanted, you could change the Bulletins option
described above to read:
A,<A>.... Announcements,,5,A
Just remember: NEVER change the Command Character Identifier (the
last character on each entry line), and NEVER use a Command Letter more
than once in each menu.
Page 31
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SPITFIRE uses the following Menu Files and display menus:
SFMAIN.MNU - Main Menu (SYSTEM)
SFMSG.MNU - Message Menu (SYSTEM)
SFFILE.MNU - File Menu (SYSTEM)
SFSYSOP.MNU - Sysop Menu (SYSTEM)
SFDOOR.MNU - Door Menu (SYSTEM)
SFORDER.MNU - Questionnaire Menu (SYSTEM)
MAIN<x>.CLR - Color Main Menu (DISPLAY)
MAIN<x>.BBS - Non-ANSI Main Menu (DISPLAY)
FILE<x>.CLR - Color File Menu (DISPLAY)
FILE<x>.BBS - Non-ANSI Main Menu (DISPLAY)
MSG<x>.CLR - Color Message Menu (DISPLAY)
MSG<x>.BBS - Non-ANSI Message Menu (DISPLAY)
SOP<x>.CLR - Color Sysop Menu (DISPLAY)
SOP<x>.BBS - Non-ANSI Sysop Menu (DISPLAY)
SFDR<x>.CLR - Color Doors Menu (DISPLAY)
SFDR<x>.BBS - Non-ANSI Doors Menu (DISPLAY)
SFORD<x>.CLR - Color Questionnaire Menu (DISPLAY)
SFORD<x>.BBS - Non-ANSI Questionnaire Menu (DISPLAY)
SFBATCHU.CLR - Color Batch Upload Menu (DISPLAY)
SFBATCHU.BBS - Non-ANSI Batch Upload Menu (DISPLAY)
SFBATCHD.CLR - Color Batch Download Menu (DISPLAY)
SFBATCHD.BBS - Non-ANSI Batch Download Menu (DISPLAY)
SFIMPEXP.CLR - Color Local Log-on Import/Export Menu
(DISPLAY)
SFIMPEXP.BBS - Non-ANSI Local Log-on Import/Export Menu
(DISPLAY)
Refer to SPITFIRE DOORS section of this manual for information
regarding the structure of SFDOOR.MNU. Refer to the SPITFIRE
QUESTIONNAIRES section of this manual for information regarding the
structure of SFORDER.MNU.
You can use EDLIN, any text editor or screen generating program
that is capable of saving in ASCII format to edit these files.
Should you edit these menu files and come up with some very nice
looking menus, please share the information so other Sysops using
SPITFIRE may benefit from your discovery.
SPITFIRE supports both color and Non-ANSI display menus. The
names of the files displayed for the color menus are:
MAIN<x>.CLR FILE<x>.CLR MSG<x>.CLR
SFDR<x>.CLR SOP<x>.CLR SFORD<x>.CLR
SFBATCHU.CLR SFBATCHD.CLR SFIMPEXP.CLR
Page 32
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
The names of the Non-ANSI files displayed for the non color menus
are:
MAIN<x>.BBS FILE<x>.BBS MSG<x>.BBS
SFDR<x>.BBS SOP<x>.BBS SFORD<x>.BBS
SFBATCHU.BBS SFBATCHD.BBS SFIMPEXP.BBS
"x" represents the security level of the current caller. For
example, if a caller with a security level of 10 calls and selects
ANSI/Graphics, then SPITFIRE searches for files named MAIN10.CLR,
FILE10.CLR, MSG10.CLR, SFDR10.CLR, etc. to display as the color menus.
If a caller with a security level of 10 calls and chooses not to use
ANSI Graphics, then SPITFIRE searches for files named MAIN10.BBS,
FILE10.BBS, MSG10.BBS, SFDR10.BBS, etc. In the event these files are
not found, then SPITFIRE displays the default menus.
The reason for different color and Non-ANSI display menu files
for each security level is to control what commands are shown to the
caller. For example, if the BBS requires a security level of 10 to be
able to download a file, then FILE10.CLR and FILE10.BBS will show the
<D>... Download A File command while FILE9.CLR and FILE9.BBS would not
show the command. A color menu file and a Non-ANSI menu file will have
to be created for each security level that you assign to callers if you
decide to use SPITFIRE display file menus rather than using SPITFIRE's
default menus. The exception to the security defined Non-ANSI and
menus, are the menus used for the batch file transfer and the local
log on import/export menu. The batch file transfer menus are simply
named SFBATCHU.BBS/CLR and SFBATCHD.BBS/CLR. The import/export menu
which displays when logged on locally is named SFIMPEXP.BBS/CLR.
Buffalo Creek Software provides a utility to create the color
and non-color menu files. The name of this utility is MKSFMENU.
You can download it from Buffalo Creek's BBS at 515-225-8496.
Your SPITFIRE distribution package includes sample MAIN10.CLR,
FILE10.CLR, SFBATCHU.CLR, SFBATCHD.CLR, MSG10.CLR, SFIMPEXP.CLR,
SOP.CLR, MAIN10.BBS, FILE10.BBS, SFBATCHU.BBS, SFBATCHD.BBS and
MSG10.BBS, SFIMPEXP.BBS and SOP.BBS files.
4.6 SPITFIRE FILE CLARIFICATIONS
---------------------------------
The following files deserve a more in-depth explanation:
DAILYLMT.DAT - This file controls, per security level, the amount
(SYSTEM) of time a caller has each day, each call, kilobytes
allowed to be downloaded per day, files allowed to
be downloaded per day, node chats allowed, time
Page 33
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
allowed per node chat, quick log on access, when and
if a caller will be warned of file ratio violation,
and when/if the file ratio violation will be
enforced.
Below is a list of abbreviations used in DAILYLMT.DAT and what each
abbreviation represents:
MPC - Minutes Per Call
MPD - Minutes Per Day
QL - Quick Log-on
DLPD - Downloads Per Day
KB - Kilobytes (allowed to be downloaded per day)
#OCA - Number Of Chats Allowed
TPNC - Time In Minutes Per Node Chat
VWR - Violation Warning Ratio
VER - Violation Enforcement Ratio
A line should be created in DAILYLMT.DAT for each security level
you allow on your BBS. Each line should begin with the numeric value
of the security level whose parameters are being defined. The syntax
for each line in the DAILYLMT.DAT is:
10,MPC=45,MPD=60,QL,DLPD=15,KB=2000,Y,#OCA=5,TPNC=5,VWR=15,VER=25
where:
10 represents the security level for which the subsequent
parameters apply.
MPC=45 represents the time in minutes a caller with this security
level is allowed for each call to the BBS. This overrides the
Log On Time Limit defined at SPITFIRE's ALT+Z configuration.
MPD=60 represents the total daily time limit in minutes a caller
of this security level is allowed. This overrides the
Daily Time Limit defined at the ALT+Z SPITFIRE configuration
screen.
QL allows a remote caller with this security level to quickly log
on the BBS. This remote quick log on is similar to a local
quick log. After the initial log on, a caller with this
security is immediately displayed the Main Menu, avoiding the
display of WELCOME2.BBS/CLR to WELCOME9.BBS/CLR, ALL.BBS/CLR,
etc. It should be noted, <x>SEC.BBS/CLR and <x>.BBS/CLR will
display to callers with quick log on capability. To require a
normal log on, simply omit the QL from the DAILYLMT.DAT line.
DLPD=15 represents the maximum number of files a caller with this
security will be allowed to download each day.
Page 34
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
KB=2000 represents the total number of kilobytes a caller with this
security level will be allowed to download each day.
#OCA=5 sets Number Of Chats Allowed (node chats) each day on a
multi-node system for this security level. SPITFIRE defaults
to 5. To disable node chats for a particular security level,
set this parameter to #OCA=0. The #OCA=<x> is only applicable
to multi-node systems.
TPNC=5 designates the Time (in minutes) Per Node Chat allowed for
this security level. SPITFIRE defaults to 5 minutes per node
chat. The TPNC=<x> is only applicable to multi-node systems.
VWR=15 represents the Violation Warning Ratio for this security level.
When the upload/download ratio exceeds 1 upload for each VWR
value downloaded, SFRATIO.BBS/CLR (if found) is displayed to
the caller. Both the number of files AND the kilobytes
downloaded must exceed the ratio before SFRATIO.BBS/CLR is
displayed to the caller. If you do not wish to warn the
caller, do not include the VWR parameter in the DAILYLMT.DAT
for this security level.
VER=25 represents the Violation Enforcement Ratio for this security
level. When the upload/download ratio exceeds 1 upload for
each VER value downloaded, SPITFIRE alters the caller's
security to what the Sysop has configured at the U/D Ratio
Violation Security in the ALT+Z configuration screen. Both
the number of files AND the kilobytes downloaded must exceed
the ratio before the caller's security is altered. If
you do not wish to enforce the ratio violation for this
security level, do not include the VER parameter in the
DAILYLMT.DAT for this security level.
**NOTE** A warning should be displayed prior to enforcing the upload/
download ratio which would alter the caller's security level.
It is highly recommended that the difference between the
violation warning and the violation enforcement should be
greater than the amount of files the caller may download in
a batch download. Using the word Batch at the end of a line
in SFEXTDN.BBS limits downloads per batch to 6, so a difference
of at least 6 is recommended. Using the word Usefile, at the
end of a line in SFEXTDN.BBS limits downloads per batch to 99,
so a difference of 99 is recommended. (See section: External
Batch Download Protocols of this manual for a full explanation.)
If the difference between the violation warning and the violation
enforcement is not equal to or greater than the amount of files
a caller can download in a single batch, it is possible during
a batch download for a caller to have their security altered
without ever being warned of the impending status change.
Page 35
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
If SPITFIRE finds the VWR and VER are defined for the security
level of the caller, each time a file is downloaded, SPITFIRE
performs the following calculations to determine if a caller has
violated the upload/download ratio requirement:
The number of files downloaded by a caller is divided by the
number of files uploaded AND the number of kilobytes downloaded
by the caller is divided by the number of kilobytes uploaded by
the caller. SPITFIRE must verify that both the file ratio and
the kilobyte ratio have been violated. If the results of both
the file and kilobyte calculation are greater than the value
defined for the VER (Violation Enforcement Ratio), SPITFIRE will
then alter the caller's security level to that configured at the
U/D Ratio Violation Security.
SPITFIRE will return the caller to their original security once
the caller's upload/download ratio is again within the required
ratio limits. The SFUSERS.DAT file contains a field which stores
information regarding the caller's original security level. When
a caller uploads a file to the BBS, SPITFIRE first checks to see
if the caller's current security level is less than the original
security level. If so, SPITFIRE performs the same computations
as described above. If the results of the file or kilobyte
calculation is less than the VER (Violation Enforcement Ratio),
the caller's original security level is restored.
Using the example from above, all callers with a security level of 10
are allowed 45 minutes per call, 60 minutes per day, 15 downloads
per day, 2,000 kilobytes per day, 5 node chats of up to 5 minutes
per node chat, will be displayed SFRATIO.BBS/CLR when the upload/
download ratio of 1 to 15 is exceeded, and will have their security
altered when the upload/download ratio of 1 to 25 is exceeded.
DAILYLMT.ZIP is included in the SPITFIRE package and can be downloaded
from Buffalo Creek's BBS. DAILYLMT.COM is a menu driven program that
is used to create and maintain DAILYLMT.DAT.
SFRATIO.BBS/CLR - It's rare when a caller's uploads exceed their
(DISPLAY) downloads. Some callers get in the habit of taking
and never give much consideration toward uploading.
This file is displayed after a download is completed
that has tipped the scales on the caller's U/D ratio
provided the DAILYLMT.DAT for the caller's security
level contains a VWR (Violation Warning Ratio).
SFRATIO.BBS/CLR will then be displayed to the caller
showing your "friendly" words of advice whenever
this situation presents itself. If you are not
concerned about a caller's U/D ratio, simply don't
include this file in your SF display file directory.
Page 36
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
JOKER.DAT - JOKER.DAT contains a list of all names you don't
(WORK) want to allow on your board. It may be used to
list names like: Dr. Phreak, Micro Muck, Lord Havoc,
Killer, etc.. Also, if any line in JOKER.DAT is
preceded with an @ followed by text, no one with
that portion of the text in any part of their name
will be allowed to log on to the BBS. These feature
is primarily intended to scrutinize those who
attempt to log on a BBS using profane words. The
'@<text>' feature should be used with caution since
it would be quite easy to unintentionally deny
someone access. JOKER.DAT is an ASCII file that has
each name listed on a separate line, such as:
Dr. Phreak
Micro Muck
Lord Havoc
@screw
@damn
All Callers
When locking a caller out of the SPITFIRE BBS
system or marking the caller for deletion, SPITFIRE
prompts you as to whether you wish to add the name
to JOKER.DAT. If you respond with a Yes, the name
is automatically added to JOKER.DAT. SPITFIRE also
allows a caller to be locked out or marked for
deletion using ALT+A at the "Ready..." prompt or
from the Sysop Menu. A caller may also be locked
out by pressing ALT+L while the caller is logged on
the BBS. A caller may be added to JOKER.DAT using
any of these features.
LAKOTA.COM - If LAKOTA.COM exists in the SPITFIRE home directory,
(SYSTEM) callers may download messages in QWK format, use
an offline mail reader to read/reply to messages,
and upload reply packets into SPITFIRE's message
base. LAKOTA, a SPITFIRE QWK Mail System, is
available using Option L of the Message Menu. If
you do not wish to have this option available to
callers, the security in SFMSG.MNU for this feature
should be set high enough so the caller is not able
to access it. For more information refer to the
documentation that accompanies LAKOTA.COM.
LOCKOUT.BBS/CLR - SPITFIRE reads JOKER.DAT line-by-line and compares
(DISPLAY) the names in the file against the caller's first
and last name. If a match is found, then the
LOCKOUT.BBS/CLR is displayed to the screen and the
caller is logged off!
Page 37
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFNWSLTR.BBS/CLR - File which displays to the caller when they request
(DISPLAY) the <N>...Newsletter from the Main Menu. SPITFIRE
will notify the caller if this file has been updated
since they last logged on the BBS. This file can be
used to send special messages to callers regarding
the system.
SFNOUP.DAT - SFNOUP.DAT contains a list of files which the
(WORK) Sysop does not wish to have uploaded to the BBS.
SFNOUP.DAT will allow complete use of DOS's wildcard
feature. You can create an ASCII file that has each
name listed on a separate line, such as:
TROJAN.*
WIN*.*
PERVERT.COM
*.GIF
When erasing a file from the file menu, SPITFIRE
prompts you as to whether you wish to have the file
added to SFNOUP.DAT. Responding with a Y for Yes
will add the erased file's name to SFNOUP.DAT.
SFFILES.BBS - Resides in each File Area and lists files available
(DL FILE AREA) for download from that area. This file is set up
using your favorite text editor. Here are some
guidelines one must follow for this to work
properly with SPITFIRE.
1--------10--------20--------30--------40--------50--------60--------70
SF33-1.ZIP 325,000 03-03-93 SPITFIRE Bulletin Board System (V3.3)
The FILENAME must begin at column 1
The FILESIZE must end at column 21
The FILEDATE must end at column 31
The FILE DESCRIPTION must start at column 34
When the SFFILES.BBS displays to a caller who is
using ANSI Color Graphics and a file line is not
colored like the others, but rather uses the
caller's default color, it is because the comma in
the file size is either not located properly or does
not exist. SPITFIRE uses the comma in the file size
to determine whether the line is a file listing.
SFPCKMSG.COM - SPITFIRE shells to SFPCKMSG.COM for purging
messages either as Event M or when selected from
the SPITFIRE Sysop Menu. Criteria for packing
messages is determined according to how the Sysop
has configured the Message Conference record.
The purge criteria is set independently for each
conference available on the BBS.
Page 38
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFPCKUSR.COM - SPITFIRE shells to SFPCKUSR when the Sysop selects
the Pack User File option from the SPITFIRE Sysop
Menu. SFPCKUSR is used to purge callers marked for
deletion and inactive callers. A caller is
considered inactive if they have not called the
BBS in <x> amount of days. The Sysop determines
the value of <x>.
SFUPCASE.DAT - A list of keywords that are converted to or left
(WORK) in uppercase when converting file descriptions.
This is a simple text file that lists these
keywords, one per line.
SFREMOTE.BAT - This batch file is used with the remote Drop to
(SYSTEM) DOS feature and should be used with a carrier
detect utility such as WATCHDOG, RemDoor or Doorway.
If connection is terminated while a caller is at
the DOS level the system is reset provided such a
utility is used. If you have included SF.BAT in the
AUTOEXEC.BAT, SPITFIRE will automatically boot on
system start up. Using such a utility is highly
recommended but none are included in the SPITFIRE
package because they were written by other authors.
However, these utilities may be downloaded from
Buffalo Creek as well as from numerous other BBS
systems. When shelling to SFREMOTE.BAT, SPITFIRE
sends a parameter to SFREMOTE.BAT which is the
number of the comm port.
SF.BAT - Batch file which invokes SPITFIRE. This file
(SYSTEM) contains the necessary data for the scheduled
events feature within SPITFIRE to work properly.
Refer to section - EVENT MENU EXPLANATION - of
this manual for more information on Scheduled
Events. It also contains the data necessary to
execute programs using the SPITFIRE Door feature.
Refer to the section - SPITFIRE DOORS SECTION -
of this manual for more information on SPITFIRE
Doors.
SFMAIN.BAT - Batch file which executes the Sysop configurable
(SYSTEM) Main Menu option.
SFFILE.BAT - Batch file which executes the Sysop configurable
(SYSTEM) File Menu option.
SFMESS.BAT - Batch file which executes the Sysop configurable
(SYSTEM) Message Menu option.
Page 39
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFMSGPCK.BAT - Batch file that executes immediately after packing
(WORK) the message base. SFMSGPCK.BAT might be used
to create a file archive of the SPITFIRE message
base after it is packed. SFMSGPCK.BAT may be used
by some net-mail drivers to perform some necessary
duties required after packing the message base.
SFINIT.BAT - Batch file executes, if it exists, after a caller
(SYSTEM) hangs up and prior to the modem being initialized.
This allows utilities (such as a last 10 caller
listing or checking the integrity of uploaded files)
to be executed between callers to the BBS.
SFPGOFF.BBS/CLR - This file displays to the caller in the event
(DISPLAY) the caller pages the Sysop and the Sysop has the
page feature turned off.
SFUNANS.BBS/CLR - This file displayed to the screen in the event a
(DISPLAY) caller has paged the Sysop and the Sysop does not
answer the page.
SFPAGED.BBS/CLR - This file displays to the caller in the event
(DISPLAY) the Sysop has the page turned on and the caller
attempts to page the Sysop again when the first page
remains unanswered. If this file exists in the
display file directory, the Sysop will only receive
the first page. Any additional pages will cause
SFPAGED.BBS/CLR to display to the caller. If
you wish to be receive multiple pages, simply do not
include the SFPAGED.BBS/CLR files in the display
file directory.
BBSNAME.DAT - Simple one line text file that is placed in the
(WORK) Work file directory and contains information
about the BBS from which the net-mail message
originates. SPITFIRE will tag this on the end of
each net-mail message.
SFSEC<x>.BAT - This batch file, if it exists, executes after the
(SYSTEM) caller logs on the BBS, provided the caller's
security is equal to <x> in the batch file name.
One example for utilizing this would be if your BBS
serves as a hub for net-mail. All callers who use
your BBS for mail could be assigned a set security
level. Upon logging on the BBS, the caller could
immediately begin the mail transfer process.
Page 40
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
BADINIT.BAT - This batch file, if it exists, executes in the
(SYSTEM) event the modem fails to respond when initialized
between callers. Commands could be placed in the
batch file to issue modem commands to reset your
modem or to reboot your system with Buffalo
Creek Software's KOLDBOOT utility. (KOLDBOOT may
be downloaded from Buffalo Creek's BBS.)
<x>SEC.BBS/CLR - This feature allows the Sysop to send a special
(DISPLAY) notice to all callers of a certain security
level. This file is not automatically erased.
(<x>=the security level of the callers to whom you
wish to send the special message.)
<x>.BBS - This feature allows the Sysop to send a special
(DISPLAY) message to a specific caller. Once the caller has
received it, SPITFIRE automatically erases it.
Example: John Doe is Caller Record # 95 on your system. If you have
a file named "95.BBS", SPITFIRE will display this file
when John Doe logs on and then erase it after it has been
received. Your callers log will have a notation that the
special message was sent.
**NOTE** In the event you use <x>.BBS to send special messages to
callers and you purge callers from the caller data base by
packing SFUSERS.DAT, please note that the <x>.BBS may no
longer match the caller for whom the message was intended.
4.7 ABOUT SPITFIRE DISPLAY FILES
---------------------------------
As you can see, SPITFIRE allows you complete flexibility when it
comes to display files. The Sysop may use this flexibility in making
their board as unique as desired. In addition, SPITFIRE also uses
control characters which may be built into display files for even
more control. These are:
^B - Inhibits the display of the "More Prompt"
^C - Disables a callers' ability to break out of the display
^D - Displays caller's first name
^E - Enables the "More Prompt" if previously turned off by ^B
^F - Displays the caller's city and state/province
^G - Transmits a beep over the caller's PC speaker
^J - Displays the number of files uploaded by the caller
^K - Displays the number of files downloaded by the caller
^L - Clears the display screen
^N - Allows caller to interrupt screen display - cancels a ^C
Page 41
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
^O - Displays the caller's original log on date
^P - Exhibits a "More Prompt" in the display
^Q - Displays the number of minutes allowed this log on
^R - Displays the caller's phone number
^S - Displays the date of the caller's last call
^T - Displays the caller's password
^U - Displays the caller's date of birth
^V - Displays the caller's full name
^W - Displays the number of K uploaded
^X - Displays the number of K downloaded
^Y - Displays the caller's security level
A few of the control characters mentioned above deserve a more detailed
explanation. When a ^B is placed in a display file, then the <More?>
prompt will not interrupt the display of the file. When SPITFIRE finds
a ^C, the caller will not be able to abort the screen. A ^N nullifies
the affect of a previous ^C and allows the caller to interrupt screen
display once again. When SPITFIRE finds a ^P, the <More?> prompt is
displayed to the screen. It should be mentioned that if a ^B is
present in the same display file as a ^P, it will always override the
^P prompt, nullifying the affect of the ^P feature. However, a ^E can
be used to nullify the affect of the ^B and allow the ^P to display the
<More?> prompt. When SPITFIRE encounters a ^G, a beep is transmitted
over the caller's PC speaker and a ^L clears the display screen. The
remaining control characters are self explanatory, i.e., a ^D displays
the caller's first name to the screen at that point in the display file
and a ^F will display the caller's city and state/province to the
screen at that point, etc.
Some planning is required when using display control characters. For
instance, do not use control characters that write information to the
screen (such as ^D, ^F, ^J, ^K, etc.) inside of a box. The characters
inserted will throw the box completely out of line.
^B is the extended ASCII value of 002.
^C is the extended ASCII value of 003.
^D is the extended ASCII value of 004.
^E is the extended ASCII value of 005.
^F is the extended ASCII value of 006.
^G is the extended ASCII value of 007.
^J is the extended ASCII value of 010.
^K is the extended ASCII value of 011.
^L is the extended ASCII value of 012.
^N is the extended ASCII value of 014.
^O is the extended ASCII value of 015.
^P is the extended ASCII value of 016.
^Q is the extended ASCII value of 017.
^R is the extended ASCII value of 018.
^S is the extended ASCII value of 019.
^T is the extended ASCII value of 020.
Page 42
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
^U is the extended ASCII value of 021.
^V is the extended ASCII value of 022.
^W is the extended ASCII value of 023.
^X is the extended ASCII value of 024.
^Y is the extended ASCII value of 025.
4.8 BACKUP FILES
-----------------
When performing Sysop maintenance such as modifying Message
Conferences or modifying File Areas, SPITFIRE makes "Backup" copies
for you. If disk space is a problem on your board copy the backup
files to disk or delete them. SPITFIRE backup files include:
SFMCONF.$$$ - Message Conferences Backup File
SFFAREA.$$$ - File Areas Backup File
4.9 THOUGHTS.BBS
----------------
SPITFIRE displays a thought to callers if a file named
THOUGHTS.BBS is found in the directory configured as your display
file path. The program to create THOUGHTS.BBS can be downloaded
from Buffalo Creek's BBS at 515-225-8496 or you can download a
ready-made THOUGHTS.BBS file.
5.0 COMMAND LINE PARAMETERS
----------------------------
Command Line Parameters can be used to make SPITFIRE start-up with
a different configuration. Command Line Parameters are what you type
at the DOS prompt (or send to the program from a batch file) when you
boot SPITFIRE.
/Cx - Sets which COMM port to use (<x> represents the
number of the COMM port).
/E - Used with front end programs for detecting error
correction modem connections, making the Ymodem-g
file transfer protocols available. This /E must
be used in conjunction with baud rate parameter.
/Ix - Initializes the System speed (<x> is modem speed).
/M - Sets the initialization string used with your
modem.
/N - Allows SPITFIRE to be terminated without hanging
up the phone or re-initializing the modem. This
Page 43
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
allows a second copy of SPITFIRE to be run as a
door. NOTE: A baud rate parameter must be specified
prior to the /N or it has no affect.
/P - Sets the drive and directory used as the SPITFIRE
Work File Path.
/Tx - Used with frontend programs and sets the amount of
time allotted to the caller. This allows systems
running under a frontend program to pass the
amount of time remaining before a frontend scheduled
event. This only applies to the first caller on
immediately after SPITFIRE is booted since SPITFIRE
will terminate and return control to the frontend
program when the caller logs off. This could
also be used when running SPITFIRE as a door.
(x indicates the amount of time in minutes the
caller is allowed.)
(baud rate) - This represents the numerical value for the highest
possible baud rate of your system. This allows
SPITFIRE to be booted without initializing the
modem so it can be used in conjunction with net
mail software programs. Refer to the section -
SPITFIRE NET-MAIL CAPABILITIES - of this manual
for further information. The range of allowable
baud rates for SPITFIRE are 0 (allows local log
ons only) to 115200.
The use of these Command Line Parameters is not usually necessary.
An exception might be when you are originally booting SPITFIRE for the
very first time or if your configuration has changed. When originally
booting SPITFIRE you should only use Command Line Parameters if you are
using a COMM port other than COMM 1 and a modem speed different than
2400 baud. In other words, SPITFIRE is written to default to COMM port
1 and to initialize the system at 2400 baud so you will not have to use
Command Line Parameters unless these defaults are different from what
you plan to use while running SPITFIRE.
SPITFIRE /C2 /I9600
The above example would boot SPITFIRE utilizing COMM port #2 and
initializing the system at a baud rate of 9600.
It should also be mentioned that any Command Line Parameters
assigned from the DOS prompt or included in the SF.BAT file will
override those set by using ALT+M or ALT+P at the SPITFIRE "Ready
Prompt". Anytime a change is made in the baud rate, work path,
modem initialization string or COMM port assignment, you MUST also
change the specifications set in the SF.BAT file. It is for this
reason that the use of command line parameters in SF.BAT is not
recommended.
Page 44
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
5.1 SF.BAT
-----------
It is advisable to use the SF.BAT to boot SPITFIRE. Some of the
advantages for using a batch file to invoke SPITFIRE are listed below:
If an error occurs, and you're using the SF.BAT included with
your SPITFIRE package, SPITFIRE will automatically reset with
the SF.BAT file. The SF.BAT file, included with your SPITFIRE
package, is vital for running Scheduled Events and Door
programs. More information regarding Scheduled Events and
Door programs may be found in other sections of this manual.
If you have the AUTOEXEC.BAT file written to automatically
boot SPITFIRE upon system startup and there is a power outage,
then SPITFIRE will automatically reboot when power is restored.
To configure the AUTOEXEC.BAT file to automatically boot SPITFIRE
upon system startup, the last two commands in the AUTOEXEC.BAT
file should resemble this:
CD\SF
SF
The above example assumes you are running SPITFIRE on the drive
you are booting from and you are running SPITFIRE in a directory
named SF.
6.0 SETTING UP THE SYSTEM RECORDS
-----------------------------------
Message Conference records and File Area records comprise your
SPITFIRE system records. There are two ways to set up the system
records in SPITFIRE. The first is by using ALT key combinations
at the SPITFIRE "Ready..." prompt. The second is through the Sysop
Menu which is accessed from the Main, Message or File Menus.
SPITFIRE allows a total of 512 different Message Conferences and
65535 File Areas.
6.1 CONFIGURING MESSAGE CONFERENCE RECORDS
-------------------------------------------
Message Conference records are configured by pressing ALT+R at the
"Ready" prompt or by selecting option <M> from the Sysop Menu. When
this is done the following will display to the screen:
Page 45
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Conference Description.. : "Untitled Message Conference"
Msg Conference Access... : Equal To Or Greater Than Caller Security
Public Messages Only.... : No Read Only Conference.... : Yes
Conference Security..... : 5 Net-Mail Conference..... : No
Maximum Msg Length...... : 99 Purge Msgs Older Than... : 120 days
Caller Message Deletion. : Yes Purge Unreceived Msg.... : No
Delete Old Thread Msg... : Yes Net ID Name............. : UNTITLED MSG
Allow Message Routing... : No Privileged Securities... : 0;0;0;0;0
>>>> RECORD [1 Of 1] MESSAGE SYSTEM RECORD MENU <<<<
<N>.......... Net-Mail Toggle <M>... Conference Description
<S>...... Conference Security <@>........ Conference Access
<#>............ Record Number <A>........... Add New Record
<P>.... Public Msg Conference <C>.......... Caller Deletion
<I>.....Insert New Conference <D>........ Delete Conference
<O>.........Old Message Purge <U>......Unreceived Msg Purge
<+>.......... Next Conference <->...... Previous Conference
<T>..... Purge Old Thread Msg <L>........Maximum Msg Length
<R>.... Allow Message Routing <*>......Read Only Conference
<!>...............Net ID Name <&>.... Privileged Securities
ENTER COMMAND - [N M S @ # R A P C I D O U + - T L * ! & <Q>uit ]?
Command <N> - Net-Mail Toggle
Allows the Sysop to configure whether an individual
message conference will allow net-mail. If a message
conference is set up to allow net-mail, callers are
allowed to leave messages to a person who is not a caller
on the BBS. If a message conference is not configured to
allow net-mail a caller can only leave messages to other
callers of the BBS. (This also applies to Carbon Copy
messages.)
Command <M> - Conference Description
You will notice that the default Message Conference
description is "Untitled Message Conference". Change
this to suit your needs. As an example, you may wish to
change the description of this conference to "Public
Messages".
Command <S> - Conference Security
This allows you to set the security level for this
Message Conference. You will notice that the default
security level is 5, which means that any caller with a
security of 5 or greater will be able to read messages
in this conference. If you wish to set a different
security level for this Message Conference, then select
<S> to change the security level of the conference.
Page 46
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <@> - Conference Access
You will note that SPITFIRE defaults the Message
Conference Access to "Equal To Or Greater Than". What
this means is that any caller with a security level equal
to or greater than the security level of this Message
Conference can access it. If you select <@>, SPITFIRE
will toggle this feature to "Equal To Caller Security"
and only callers with a security level equal to the
security level of the Message Conference will be able to
access this conference. Callers with a security level
greater than or less than the security level of this
conference will not be able to access this conference
(unless the caller has Sysop security or whose security
is equal to a specified Privileged Security).
Command <#> - Record Number
Allows you to enter a specific Message Conference record
number. After entering the number, the information for
the record number you specified is displayed.
Command <A> - Add New Record
Allows the Sysop to add a new Message Conference to the
Message base. The new record will be added after the
last existing Message Conference record. For instance,
if your system has 25 Message Conferences and the <A>
option is selected, a Message System Record Number 26
will be added.
Command <P> - Public Messages Only
Toggles whether the Message Conference will allow
non-public messages. The default setting of SPITFIRE is
to allow non-public messages. By selecting <P> you can
toggle this feature so that only messages marked as
public are allowed.
Command <C> - Caller Deletion
Toggles whether a caller of the BBS is allowed to delete
messages. If set to Yes, the caller will be able to
delete messages either sent to or sent by them. If
this is toggled to No, a caller will not be allowed to
delete any messages. This option is set for each message
conference individually. You may toggle it one way for
one message conference and the other for another message
conference.
**** Although Buffalo Creek Software offers the Caller Deletion option
which the Sysop can use to configure whether a caller is allowed
to delete messages in SPITFIRE, it assumes no responsibility for
Sysops who use this feature. Legal judgments concerning the
ownership of messages on a bulletin board system could possibly
hold Sysops liable for denying callers control of their posted
messages.
Page 47
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <I> - Insert Msg Conference
Inserts a new Message Conference record between two
existing Message Conference records. Upon selecting
this option, SPITFIRE displays the prompt "Insert before
which conference?". A new Message System Record is
inserted preceding the Message System Record number
entered here.
***IMPORTANT NOTE***
When inserting a new Message Conference the SFMSG<x>.DAT,
SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR files are
automatically reset to correspond to the appropriate
Message Conference. For example, assume the BBS has
five active Message Conferences and a new Message
Conference is inserted prior to Message Conference #4.
The new Message Conference becomes Message Conference
#4. The previous Message Conference #4 now becomes
Message Conference #5, therefore, the SFMSG04.DAT,
SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR are renamed to
SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX and SFMSG05.PTR.
The previous Message Conference #5 now becomes Message
Conference #6 and the SFMSG05.DAT, SFMSG05.PTR,
SFMSG05.IDX and the SFMSG05.LMR are renamed to
SFMSG06.DAT, SFMSG06.PTR, SFMSG06.IDX and SFMSG06.LMR.
Command <D> - Delete Conference
This option allows an existing Message System Record to
be deleted. Upon selecting this option SPITFIRE displays
the prompt "Delete which conference?". The number entered
here will cause that Message Conference to be removed.
***IMPORTANT NOTE***
When deleting an existing Message Conference the
SFMSG<x>.DAT, SFMSG<x>.PTR, SFMSG<x>.IDX and SFMSG<x>.LMR
files are automatically reset to correspond to the
appropriate Message Conference. For example, let's again
assume the BBS has five active Message Conferences and
Message Conference #4 is deleted. The pre-existing
SFMSG04.DAT, SFMSG04.PTR, SFMSG04.IDX and SFMSG04.LMR
files are deleted when Message Conference #4 is deleted.
The previous Message Conference #5 now becomes Message
Conference #4. The SFMSG05.DAT, SFMSG05.PTR, SFMSG05.IDX
and SFMSG05.LMR are appropriately renamed to SFMSG04.DAT,
SFMSG04.PTR, SFMSG04.IDX and SFMSG04.PTR.
Command <O> - Old Message Purge
Specifies how many days old a message in this particular
conference must be prior to it being purged during
SPITFIRE's internal message packing procedure. For
Page 48
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
instance, if this is set to 120 days, when SPITFIRE packs
this message conference any messages older than 120 days
will be purged.
Command <U> - Unreceived Msg Purge
Specifies whether messages which are unreceived are
allowed to be purged from the Message Conference. If
set to Yes, when packing the message base any messages
older than the days set with the <O>..Old Message Purge
option will be purged even if they have not yet been
received. If set to No, unreceived messages will not be
purged.
Command <+> - Next Conference
This option is used to move forward from one Message
System record to another. Pressing the "+" key
initiates the progression from one Message Conference
record to the next in sequential order. Upon reaching
the last record, if the "+" key is pressed, SPITFIRE
will cycle to the first Message System record.
Command <-> - Previous Conference
This option is used to cycle through the Message
System records in reverse order. Pressing the "-" key
causes the previous conference number to be displayed.
From the first Message System record, if the "-" key is
pressed, SPITFIRE will cycle to the last Message
System record.
Command <T> - Purge Old Thread Msg
This option allows the Sysop to designate whether
threaded messages will be deleted when using SPITFIRE's
internal message packer. If this is toggled to Yes,
when the message base is packed, threaded messages
older than the days set with the <O>..Old Message Purge
will be deleted. If toggled to No, threaded messages
will not be deleted from the message base.
Command <L> - Maximum Msg Length
The option allows the Sysop to configure the maximum
lines that will be allowed per message in this message
conference. Valid options range from 25 lines to 99
lines. For instance, if 50 is entered, the maximum
length for all messages in this conference would be
50 lines.
Command <R> - Allow Message Routing
The Routing option is only applicable if the message
conference has been configured as a net-mail conference.
Page 49
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
When set to Yes, and you are using BCSUTI Version 1.0
or greater, the message will automatically be routed for
you. Otherwise, you will need to route your messages
in the normal fashion. The Routing feature also works
with carbon copy messages so that is possible to send
the same message to 10 different people, routing it to
10 different locations.
Command <*> - Read Only Conference
When this feature is toggled to No, callers may read and
enter messages in this conference. If toggled to Yes,
callers may read messages in this conference but no
messages can be entered. Any caller with Sysop status
may read and enter messages regardless of how this
option is set. (For more information, refer to the
section, Special Commands for Sysop Status in this
manual.)
Command <!> - Net ID Name
When this feature is selected, the Sysop can configure
the Net ID Name for this conference. The Net ID Name
is a shortened conference description name used by BCSUTI
and LAKOTA (SPITFIRE's QWK Mail System). If the Sysop
does not configure this, the Net ID Name defaults to
the first 15 characters from the Message Conference
description. (LAKOTA uses the first 13 characters of
the Net ID Name while BCSUTI and other mail exchange
programs may use the full 15 characters.)
Command <&> - Privileged Securities
This feature allows the Sysop to configure up to five
privileged security levels per Message Conference. If
a caller logs on and has a security level equal to a
security assigned here, the caller will have access to
this Message Conference regardless of how the Message
Conference Security and the Message Conference Access
options have been configured. In other words, the
privileged security will always override the Security
and the Access configuration for the Message Conference.
As an example, assume a Message Conference has been
configured only to allow callers with a security level
greater than or equal to 50. Also, assume that 30 is
configured as a privileged security. If a caller with
a security of 30 logs onto the BBS, the caller will have
access to that particular Message Conference.
Command <Q> - Quit
Upon selecting this option, SPITFIRE will return to the
place from which the Message System Record Menu was
initiated. In other words, if invoked from the Sysop
Sysop Menu, SPITFIRE will return to the Sysop Menu.
If initiated from the "Ready..." prompt, SPITFIRE will
return to the "Ready..." prompt.
Page 50
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
6.2 CONFIGURING FILE AREA RECORDS
----------------------------------
File Area records are configured by pressing ALT+F at the "Ready"
prompt or by selecting option <F> from the Sysop Menu. When this is
done the following is displayed to the screen:
Download Path..... : C:\SF
Upload Path....... : C:\SF
Area Description.. : "Untitled File Area"
Area Access....... : Equal To Or Greater Than Caller Security
Area Security..... : 5 No Charge (FREE) Area.. : No
Preview Area...... : No Privileged Securities.. : 0;0;0;0;0
CD Rom Area....... : No
Search File Area.. : Yes
>>>> RECORD [1 Of 1] FILE SYSTEM RECORD MENU <<<<
<F>......... Area Description <U>.............. Upload Path
<D>............ Download Path <S>............ Area Security
<@>.............. Area Access <R>............ Record Number
<A>............. Add New Area <I>.......... Insert New Area
<P>............... Purge Area <T>...... Toggle Preview Area
<+>................ Next Area <->............ Previous Area
<C>...............CD Rom Area <$>......... Search File Area
(N>.....No Charge (FREE) Area <&>.... Privileged Securities
ENTER COMMAND - [F U D S @ R A I P T + - C $ N & <Q>uit ]?
Command <F> - Area Description
Notice that the default File Area description is
"Untitled File Area". Change the description so it
describes the types of files stored in this particular
file area. For example, if the files in this area
could be categorized as system utilities, a suitable
description for this area might be "Utilities".
Select <F> to make this change.
Command <U> - Upload Path
To change the upload path, simply select <U> from the
menu. The Upload and Download paths are any legal DOS
pathnames telling SPITFIRE where it can find the files
associated with the File Area. It is possible to
configure uploads to go into a single "Recent Uploads"
File Area, or to different areas which you could specify
by subject. Here are a few examples of upload/download
paths:
The following example sends uploads to a sub-directory
called "UPLOADS" and allows the caller to download
programs from a sub-directory called "UTILITIES". (Note:
SF is the parent directory.)
Page 51
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Download Path.....C:\SF\UTILITIES
Upload Path.......C:\SF\UPLOADS
In the following example, uploads are sent to the same
sub-directory where the files available for downloading
exist:
Download Path.....C:\SF\UTILITIES
Upload Path.......C:\SF\UTILITIES
If you're running the BBS on a floppy-based system with
upload and download files on drive B, and not using
sub-directories, you could do the following:
Download Path.....B:\
Upload Path.......B:\
Command <D> - Download Path
You will notice that SPITFIRE sets the default download
path to the directory where SPITFIRE resides. To change
this DOS filepath, select <D> to set the path for this
File Area. In the event that the filepath set does not
exist, SPITFIRE will create it. For example, if you
set your download path to C:\UTILITIES and the utility
directory doesn't exist on your drive, SPITFIRE will
create the directory. You will also notice once you
have entered the drive letter, SPITFIRE automatically
adds the colon ":" and the backslash "\" after it. If
an invalid path is entered, SPITFIRE will not accept it.
You will have to copy the files you want available for
download into this directory and create a SFFILES.BBS
(text file) listing the files in that directory. The
SFFILES.BBS file must also reside in that directory.
(The utility, MKSFFBBS, which will create your
SFFILES.BBS for each file directory, is available for
download from Buffalo Creek - 515-225-8496.)
Command <S> - Area Security
This allows you to set the security level for this File
Area. You will notice that the default security level
is 5, which means that any caller with a security of 5
or greater will be able to access this File Area. If you
wish to set a different security level for the File Area,
then select <S> to change the security level of the area.
Command <@> - Area Access
Note that SPITFIRE defaults to the File Area Access of
"Equal To Or Greater Than". This means that callers with
a security level equal to or greater than the security
Page 52
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
level of this File Area can access it. If you select
<&>, SPITFIRE will toggle this feature to "Equal To
Caller Security". Then only callers with a security
level equal to the security level of the File Area will
be able to access this area. Callers with a security
level greater than or less than the area security level
will not be able to access it, except those callers
with Sysop security or a security equal to a configured
privileged security.
Command <R> - Record Number
This option allows you to enter a specific File Area
record number. Upon entering the number, all current
information for the record number you specified is
displayed.
Command <A> - Add New Area
By selecting the <A> option, a Sysop can add a new
File Area Conference to the File Area System Records.
The new record will be added after the last existing
File Area System Record. For instance, if your system
has 25 File Areas and the <A> option is selected, a File
Area Record Number 26 will be added. SPITFIRE will
allow an unlimited number of File Areas.
Command <I> - Insert New Area
By selecting <I>, a Sysop can insert a new File Area
System Record records between two existing file areas.
Upon selecting this option, you are prompted with
"Insert before which area?". A new File Area System
Record will be inserted preceding the File Area System
Record entered here.
Command <P> - Purge Area
This option allows an existing File Area System Record
to be deleted. Upon selecting this option, you will be
prompted with "Delete which area?". The number that you
enter here will cause that File Area to be removed from
the File Area System Records.
Command <T> - Toggle Preview Area
The "T" option is used to toggle a File Area's Preview
Area between Yes and No. If the Preview Area is toggled
to Yes, a caller with a security less than the required
Area Security will be allowed to preview this file area.
This means that the caller can access this file area,
list files, read text files, view file archives, etc. but
will not be allowed to download any files from this area.
In other words, the caller can do everything except
Page 53
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
download from this file area. If this is toggled to No,
callers with a security less than the specified Area
Security will not be allowed access to this File Area.
Command <+> - Next Area
This option is used to move forward from one File Area
System record to another. Pressing the "+" key will
progress forward from one record to the next in
numerical order. When reaching the last record and
the "+" key is pressed, SPITFIRE will cycle to the first
File Area System record.
Command <-> - Previous Area
This option cycles through the File Area System
records in reverse order. Pressing the "-" key
will display the preceding record number. From the
first File Area System record if the "-" key is pressed
SPITFIRE will cycle to the last File Area System record.
Command <C> - CD Rom Area
The option specifies the file area as a CD Rom Area.
If this is toggled on, then SPITFIRE searches the Display
File Path for a SFFILES.<x> for the file listing of this
CD Rom Area. The <x> should correspond with the number
of the file area. For instance, if file area 15 is a CD
Rom Area then it would need to be named SFFILES.15.
SPITFIRE does not include CD Rom Areas in its search for
<N>ew files or report on file statistics if the BBS has
a CD Rom Area.
Command <$> - Search File Area
Allows Sysops to configure whether the download path
area per File Area will be searched for duplicate files
when a caller attempts an upload. If this is toggled
to Yes, the download path will be searched and if this
is toggled to No, the download path will not be searched.
As an example, Sysops using a CD Rom file area may wish
to skip the search for these areas due to the time that
is required to scan these areas.
Command <N> - No Charge (FREE) Area
Allows the Sysop to configure whether a file area will
be a free file area or not. If this option is toggled
to Yes, a caller may download files from this area and
the caller's statistics (number of files downloaded and
kilobytes downloaded) will not be updated. When toggled
to No, files downloaded from this area will update the
the caller's statistics, increasing the number of files
and the kilobytes downloaded for each file that is
downloaded from this area.
Page 54
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <&> - Privileged Securities
This feature allows the Sysop to configure up to five
privileged security levels per File Area. If a caller
logs on and has a security level equal to a security
assigned here, the caller will have access to this File
Area regardless of how the File Area Security and the
File Area Access options have been configured. In other
words, the privileged security will always override the
Security and the Access configuration for the File Area.
As an example, assume a File Area has been configured
only to allow callers with a security level greater than
or equal to 50. Also, assume that 30 is configured as a
privileged security. If a caller with a security level
of 30 logs onto the BBS, the caller will have access to
that particular File Area.
Command <Q> - Quit
Selecting this option will return you to the place in
SPITFIRE from where the File System Record Menu was
called. In other words, you will be returned either
to the Sysop Menu or the "Ready..." prompt. SPITFIRE
will automatically save your newly configured System
Record.
7.0 SPITFIRE QUESTIONNAIRES
----------------------------
Questionnaire files are created with any ASCII text editor and
placed in the directory you have configured as your Work File Path.
The Questionnaire answer files will automatically be created by
SPITFIRE.
There are 2 types of questionnaires available for use in SPITFIRE.
There is the NEWUSER __/ SFNEWU.QUE The questionnaire file
Questionnaire \ SFNEWU.REP The reply file
This is automatically utilized ONLY when a new caller logs on.
There is the ORDER ___/ SFORDER<x>.QUE Poll questionnaire files
Questionnaire \ SFORDER<x>.REP Poll reply files
This is utilized only from the MAIN MENU when the caller selects
<Q>.. Questionnaire Menu.
Page 55
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SPITFIRE will allow up to 24 different questionnaire files to be
accessed from the Main Menu. The files which contain the questions
are SFORDER<x>.QUE. The replies are stored in the corresponding
SFORDER<x>.REP. <x> represents an alpha character ranging from A
to Z (with the exception of G and Q which are reserved by SPITFIRE
for Goodbye and Quit). For example:
SFORDERA.QUE SFORDERA.REP
SFORDERB.QUE SFORDERB.REP
SFORDERC.QUE SFORDERC.REP
The caller's answers are appended to the end of the appropriate reply
file. If the file does not already exist, SPITFIRE will create it.
SPITFIRE uses a simple procedure to utilize Questionnaires.
Questionnaires are simple text files that are interpreted by
SPITFIRE. The special control codes discussed in the section - ABOUT
SPITFIRE DISPLAY CODES - of this manual also apply to the SPITFIRE
questionnaire files. Any line in the questionnaire file will simply
be displayed to the caller unless it begins with a special character.
SPITFIRE uses established first characters to determine the type of
response required by the caller. These are:
: - If the first character in the line is a colon, SPITFIRE pauses
for the caller's input. The caller must respond to the question
before SPITFIRE will continue with the questionnaire.
; - If the first character in the line is a semicolon, SPITFIRE
will pause for the callers input. But unlike the colon, the
caller is not required to respond to the question. The caller
can simply hit the Enter key and SPITFIRE will continue with the
questionnaire.
@ - If the first character in the line is an "at" sign, SPITFIRE
will pause for the caller to input a date in the format of
MM-DD-YY. SPITFIRE will automatically insert the hyphens
when the caller responds. Once the caller has entered the
response, SPITFIRE will redisplay it to the caller and ask
whether the information is correct.
# - If the first character in the line is the pound sign, SPITFIRE
will pause for the caller to input a phone number. The
format will depend on how the Sysop has the system configured.
If the Sysop has used the ALT+T to configure the phone
number to US format, then SPITFIRE will require the following
format: ###-###-####. Again, SPITFIRE will automatically
insert the hyphens when the caller responds. If the Sysop does
not have the system configured to US format, SPITFIRE will
Page 56
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
accept any input up to 12 characters in length. Once
the caller has entered the response, SPITFIRE will redisplay
it to the caller and ask whether the information is correct.
^# - If a line begins with a caret sign followed by a number, SPITFIRE
will adjust the caller's security level equal to the number
following the caret sign provided the number is less than the
configured Sysop security. If the number used here is equal
to or greater than configured Sysop security level, the caller's
security level will not be changed. The number should be a valid
security level available on your system. SPITFIRE writes
a note in HEYSYSOP.LOG to advise you that the callers security
level was changed.
Tilde - If the first character in a questionnaire line begins with a
Symbol tilde character, the caller will be disconnected from the BBS.
This could be used by Sysops in the SFNEWU.QUE so callers could
be verified before they are allowed access to the BBS.
&<#> - If a line begins with a ampersand followed by a number, SPITFIRE
will adjust the caller's time left on the system by the number
following the ampersand. &20 would provide the caller with an
additional 20 minutes.
? - If the first character in the line is a question mark, SPITFIRE
will prompt the line and automatically add a "[y/n]?". SPITFIRE
will then only accept a Y or N response from the caller. This
Yes/No question is used to branch to other special questions
depending on the caller's response. For instance, when SPITFIRE
receives a Y response to a question beginning with a question
mark, it will continue on through the questionnaire until a plus
sign, "+", is found. The text or additional questions you would
like to present to the caller who has responded with a Y should
start immediately after the plus sign. This Y series of lines
is ended with a second plus sign, "+". When the second plus
sign "+" is encountered, SPITFIRE will continue on with the
questionnaire normally. Similarly, when SPITFIRE receives a
N response to a question beginning with a question mark, it will
continue on through the questionnaire until a minus sign, "-",
is found. Any text or additional questions you would like to
present to the caller who responded with an N should be contained
between two minus signs, "-". When the second minus
sign "-" is encountered, SPITFIRE will continue on with the
questionnaire normally. It should be mentioned that any text
or questions between where the caller responds with a Y and the
first plus sign will be ignored, just as any text or questions
between where the caller responds with an N and the first minus
sign will be ignored. Each line that starts with a question
mark must be followed by a set of plus signs and minus signs.
Page 57
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
For example:
?Are you the Sysop of a SPITFIRE Bulletin Board
+
You have made a wise choice!
+
-
You really should consider running SPITFIRE!
-
If none of the above described characters are found at the beginning
of the line, the line is simply displayed to the caller.
The caller's answers are written to either SFNEWU.REP or SFORDER<x>.REP,
depending upon which questionnaire the caller is replying to. In
addition to the caller's answers, the caller's name, date and time
of the response is recorded within the same file. In the new caller
questionnaire reply file, SPITFIRE will also note which node the caller
was logged on to when the questionnaire was answered.
The SFNEWU.QUE is displayed to the caller upon log on. The
SFORDER<x>.QUE displays to the caller if the Questionnaire Menu is
selected from the Main Menu. The Questionnaire Menu file name
is SFORDER.MNU. The SFORDER.MNU file can be created using your
favorite text editor using the following format:
<Title of the Questionnaire>,SEC>=x,ONETIME,PRINT
The first item on the line will be a description of the questionnaire
topic you have available on the BBS and is limited to 25 characters.
The Questionnaire Topic is followed by a comma.
Next the security required to access the questionnaire is defined with
SEC<=x or SEC>=x or SEC=x. x represents a numerical value that should
coincide within the framework of security levels which apply to the
BBS. For example, let's assume x = 10. SEC<=10 would allow callers
with a security less than or equal to 10 to access the questionnaire.
SEC>=10 would allow callers with a security greater than or equal to
10 to access the questionnaire. SEC=10 would only allow callers with
a security of 10 to access the questionnaire. (Any caller with
Sysop security may access a questionnaire regardless of how SEC
is defined.)
The ONETIME variable will only allow the caller to answer the
questionnaire one time. If ONETIME does not appear, the questionnaire
can be answered multiple times.
PRINT will send the answers to the questionnaire to the printer.
If PRINT is used, the caller's responses are sent to the printer as
Page 58
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
well as being saved to the appropriate SFORDER<x>.REP file. However,
keep in mind that your printer must be turned on and ready for use.
SPITFIRE checks to determine if your printer is properly connected
and ready for use and responds accordingly. If PRINT is not included
on the line, no attempt is made to send the questionnaire answers to
the printer.
If the ONETIME and/or PRINT options are used, be sure to include
a comma to separate them from the previous parameter.
Optional ANSI and Non-ANSI display menu files may be created
using the SFORD[x].BBS/CLR file name. The x in SFORD[x].BBS/CLR will
correspond to the security level of the caller. As with other ANSI and
Non-ANSI display menu files, a file should be created for each
security level assigned to callers on your BBS system.
8.0 SPECIAL FUNCTION KEYS
--------------------------
SPITFIRE uses the ALT key in combination with various letter keys
and Function keys for many of its commands. To use an ALT+Key, the
ALT key and the appropriate letter key must be pressed simultaneously.
(First, press down the ALT key, then, while holding the ALT key down,
press the letter key.)
The following section lists the special function keys used with
SPITFIRE, explains from where within SPITFIRE these commands can be
activated and the functions they perform.
8.1 AVAILABLE SPECIAL FUNCTION KEYS
------------------------------------
The special function keys available in SPITFIRE and a brief
description of their usage include:
F1 - Review Log Files
F2 - Change Security Level
F3 - Toggle Sysop Page/Bell
F4 - Toggle Printer
F5 - Check Today's Statistics
F6 - Take Five Minutes From Caller
F7 - Give Five Minutes To Caller
F8 - Toggle Full/Divided Screen
F9 - Capture Chat To Disk
F10 - Quit SPITFIRE
ALT+F1 - Log Caller Off With Message
ALT+F2 - Log Caller Off Without Message
Page 59
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
ALT+F3 - Remove Backup/Log Files
ALT+A - Maintains Callers Database
ALT+C - Enter/Exit Chat Mode
ALT+D - Jump to DOS - Off Hook
ALT+E - Configure Events
ALT+F - Configure File Areas
ALT+J - Jump to DOS - On Hook
ALT+L - Lock Caller Out
ALT+M - Configure Modem
ALT+P - Configure Paths
ALT+Q - Quick Local Log On
ALT+R - Configure Msg Conferences
ALT+S - Log On Locally/Sysop Next
ALT+T - Toggle SPITFIRE Switches
ALT+Z - Configure SPITFIRE
HOME - SPITFIRE Sysop Help Screen
8.2 SPECIAL FUNCTION KEY DEFINITIONS:
--------------------------------------
Prior to each individual special function key definition, you
will notice an <O>, <R> or <B>. These are used to indicate from
where within SPITFIRE each particular function key can be utilized.
Listed below is a guide that explains what these letters represent:
<O> - Caller must be ON-LINE to perform.
<R> - SPITFIRE must be at "Ready for Use" prompt to perform.
<B> - Can be used BOTH when a caller's on-line or from the
SPITFIRE "Ready..." prompt.
<R> F1 (View Log File Menu)
----------------------------
This option sets the modem off hook and presents you with the
following menu:
>> View Log File Menu <<
<C>..........CALLERS.LOG
<H>.........HEYSYSOP.LOG
<N>...........SFNEWU.REP
<O>.......SFORDER<x>.REP
<S>.........SFPURGED.USR
<Q>.................QUIT
which allows you to view SPITFIRE's log files from the "Ready..."
prompt without having to log on the BBS and accessing this feature
from the Sysop Menu. Appropriate to your selection, you are able
to review the caller's activity log, Sysop notification log,
replies to the new user questionnaire, responses to the Main Menu
Page 60
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
questionnaire files, or the purged caller listing. If <O> is
selected for viewing the questionnaire/order file replies, you are
prompted to enter the letter corresponding to which SFORDER<x>.REP
file you wish to have displayed.
Upon selecting the desired log, you are then presented with the
following options for reading the log file:
<T>..Today's Date
displays the appropriate log file from its first entry
for the current day.
<B>..Beginning Of File
displays the appropriate log file from the beginning of
the file, starting with the first entry.
<S>..Specify Date
will prompt for a date to be entered and begins
displaying the appropriate log file with the first entry
of the date entered. If the date specified here cannot
be found, SPITFIRE will search for the next newer date
than what was specified and display the file from that
point forward.
<Q>..Quit
Returns SPITFIRE to the Ready For Use prompt.
<O> F2 (Change Security Level)
--------------------------------
If a caller is ONLINE and you wish to change the caller's security
level, you can change it by pressing F2. The caller is unable to
see that you are changing the security level.
<B> F3 (Toggle Sysop Page)
----------------------------
By toggling this parameter <ON or OFF> the Sysop can designate
whether or not to be paged. If the PAGE is ON, the words "PAGE
ON" will appear on the top of your screen, provided you are using
the split screen. If the page is turned on and a caller selects
<P> for page, then the prompt bell will sound to notify you that
a caller wishes to chat with you. USERINIT.BBS/CLR will be
displayed to the screen when you respond to the page. If the
PAGE is turned off and a caller pages you, then SFPAGED.BBS/CLR
will be displayed to the caller and CHAT REQUESTED will display
if you are using the divided screen. After SFPAGED.BBS/CLR is
displayed, the caller will be prompted as to whether he/she would
like to leave a comment to the Sysop, provided the caller is not
the Sysop. SPITFIRE will not allow the Sysop to leave a comment
to him/herself.
Page 61
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<B> F4 (Toggle Printer)
-------------------------
This allows you to toggle the printer ON/OFF. Everything that
is written to the CALLERS.LOG will also be sent to the printer if
this toggle is on. This is useful if you wish to retain a hard
copy of your callers' activities while on-line. Keep in mind that
your printer must be turned on and ready for use. SPITFIRE
checks to determine if your printer is properly connected and
ready for use and responds accordingly.
<R> F5 (Check Today's Statistics)
-----------------------------------
While at the "SPITFIRE ready for use prompt...", if you press F5,
SPITFIRE will set the modem off hook and display the total number
of calls to the BBS, the number of calls for the day, number of
uploads and downloads for today, daily door usage for today, and
the number of messages entered today.
<O> F6 (Take Five Minutes from a Caller)
----------------------------------------
When a caller is on-line, you can take 5 minutes from the caller's
log on-time by pressing F6. If you press F6 in multiples, then
multiples of 5 minutes are taken from the caller's time.
<O> F7 (Give Five Minutes to a Caller)
--------------------------------------
When a caller is on-line, you can give 5 minutes to the caller's
log on-time. If you press F7 in multiples, then multiples of 5
minutes are added to the caller's time.
<B> F8 (Toggle Screen)
------------------------
This feature is used to toggle the split-screen/full-screen
option.
<O> F9 (Capture Chat To Disk/Printer)
---------------------------------------
Either when responding to a caller who has paged you or when
initiating a chat, pressing F9 will capture the conversation
and save it to a file called SFCHAT.CAP in the main SPITFIRE
directory. In the event SPITFIRE finds a printer attached and
ready, the Sysop is given the option of sending the capture to
the printer. There are two ways to activate the chat capture.
You can begin the chat using F9 (rather than ALT+C). This will
begin the chat and immediately save the chat to SFCHAT.CAP. Or
the F9 can be pressed any time during a chat, at which time it
will save the remaining chat to the SFCHAT.CAP file. If SFCHAT.CAP
does not exist, it will be created. If it does exist, the chat
will be appended to the existing SFCHAT.CAP file. Chats will be
Page 62
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
differentiated in the SFCHAT.CAP file by beginning with "Chat
started with (caller name) at (date/time)" and ending with "Chat
ended at (date/time)".
<R> F10 (Terminate SPITFIRE)
-----------------------------
Pressing F10 will terminate SPITFIRE and return you to DOS.
<O> ALT+F1 (Log Caller Off With Message)
------------------------------------------
Displays NEEDSYS.BBS/CLR and logs caller off. If a caller is
online and you need to access your system, pressing ALT+F1
displays your message via the NEEDSYS.BBS/CLR screen and
terminates the connection.
<O> ALT+F2 (Log Caller Off Without Message)
---------------------------------------------
If a caller is online and you wish to disconnect this caller,
simply press the ALT+F2 keys simultaneously and the connection
will be terminated. No message will be displayed to the caller.
<R> ALT+F3 (Remove Backup/Log Files)
-------------------------------------
When selected, this option sets the modem off hook and displays
the following menu:
>>> FILE REMOVAL MENU <<<
<C>.... Erase CALLERS.LOG
<H>... Erase HEYSYSOP.LOG
<S>... Erase SFPURGED.USR
<U>.... Erase SFUSERS.$??
<Q>................. Quit
FILE REMOVAL MENU - [C H U Q]?
<C>... Erase CALLERS.LOG
Selecting this option will cause the existing CALLERS.LOG
file to be erased. SPITFIRE will automatically create a
new CALLERS.LOG file.
<H>... Erase HEYSYSOP.LOG
Selecting this option will cause the existing HEYSYSOP.LOG
file to be erased. SPITFIRE will automatically create a
new HEYSYSOP.LOG file.
<S>... Erase SFPURGED.USR
When this option is selected, SFPURGED.USR will be erased.
SPITFIRE will automatically create a new SFPURGED.USR file
the next time the SFUSERS.DAT file is packed.
Page 63
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<U>... Erase SFUSERS.$??
When this option is selected, the SPITFIRE caller's backup
files are erased.
<R> ALT+A (Maintain Callers File)
-----------------------------------
At the "Ready..." prompt, when selecting ALT+A, SPITFIRE sets the
modem off hook and allows you to maintain the caller's file,
rather than logging on and maintaining the caller's file from the
Sysop Menu. When this option is selected, the following screen
will be displayed:
Name...... : John Doe Subscription.. : N/A
Address... : Peoria, IL Last File Area : 1
Password.. : **** Msg Conference : 1
Phone No.. : 555-151-5555 Security Level : 10
Birth date : 01-20-54 K Uploaded.... : 27
Time Left. : 25 K Downloaded.. : 122
Last Call. : 03-20-92 08:08 Expert Mode... : Off
Times On.. : 3 More Prompt... : Off
Uploads... : 1 Downloads..... : 3
Msgs Left. : 2 Original Log.. : 07-15-91
Purge Allowed. : Yes
>>>> RECORD [3 Of 233] SPITFIRE CALLER RECORD MENU <<<<
(+) Next Record (-) Previous Record (D) Downloads
(N) Caller Name (X) Expert (U) Uploads
(A) Caller Address (&) Delete Caller (M) Change Msg Data
(P) Caller Password (L) Lock Caller Out (C) Last File Area
(#) Caller Phone No (T) Times On (!) Time Left
(R) Record Number (E) Enter Subscription Date ($) More Prompt
(F) Find Caller (S) Security Level (B) Birth Date
(O) Original Log Date (@) Add New Caller (Z) Purge Allowed
ENTER COMMAND [+ - D N X U A & E P L C # T ! R M $ F S B O @ Z <Q>uit ]?
Notice that when this option is selected, SPITFIRE displays the
last caller record. Usually the first record in the caller's list is
the Sysop's. Therefore, if the Sysop would do any maintenance on the
caller's file while others are nearby, displaying the last caller's
record prevents information from the Sysop's record from being readily
visible. This is done to ensure the security of the BBS. (When
accessed online from the Sysop Menu, SPITFIRE displays the record for
the current caller.)
Although, most of the command line options are self explanatory a
description of each feature is discussed more fully below:
Command <+> - Next Record
Page 64
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
This option is used to move forward from one caller
record to another. Pressing the "+" key will allow you
to progress from one record to the next in numerical
order. When reaching the last record and the "+" key
is pressed you will cycle to the first caller record.
Command <-> - Previous Record
This option allows you to cycle through the caller
records in reverse order. Pressing the "-" key
will move you to the preceding record number. From
the first caller record if the "-" key is pressed
you will cycle to the last caller record.
Command <D> - Downloads
Upon choosing this option, the following menu appears:
<N>umber Of Files, <B>ytes, <Q>uit?
<N>umber Of Files allows you to update the statistics
regarding the number of downloads the caller has made
on the BBS. This must be a numeric value ranging from
0-9999.
<B>ytes allows you to update the statistics regarding the
total kilobytes the caller has downloaded from the
BBS. This must be a numeric value ranging from 0-9999.
<Q>uit returns you to the SPITFIRE Record User Menu.
Command <N> - Caller Name
This option allows editing of the caller's name. Select
"N" and you are prompted to enter the first and last name
of the caller. When prompted for the first name, you can
also enter the first name, space and enter the last name.
The information is automatically updated. SPITFIRE will
allow up to 30 character spaces for the caller's first
and last name to be entered.
Command <X> - Expert
By selecting this command line option you will toggle
the Expert status of the caller on and off. If the
Expert status is off, the caller will receive a full menu
display. If the Expert status is on, only the command
line options will be displayed to the caller.
Command <U> - Uploads
Upon choosing this option, the following menu appears:
<N>umber Of Files, <B>ytes, <Q>uit?
Page 65
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<N>umber Of Files allows you to update the statistics
regarding the number of uploads the caller is credited
with having made to the BBS. This must be a numeric
value ranging from 0-9999.
<B>ytes allows updating caller statistics regarding the
total kilobytes the caller is credited with having
uploaded to the BBS. This must be a numeric value
ranging from 0-9999.
<Q>uit returns you to the SPITFIRE Record User Menu.
Command <A> - Caller Address
This option provides the opportunity for editing the
caller's address. When <A> is selected, you are
prompted to enter the city and state/province for
the current caller record. SPITFIRE allows up to 30
character spaces for this information. Once the
corrections are made, you will be prompted to verify
whether the new information is correct.
Command <&> - Delete Caller
When you press the "&" key you toggle whether or not a
caller is marked for deletion from the SFUSERS.DAT file.
If a caller is marked to be deleted, the next time the
SFUSERS.DAT file is packed the caller will be purged from
the caller data base file. You will notice that when
a caller is marked for deletion a "Caller Marked For
Deletion!" message will appear on the menu screen. Also,
when marking a caller for deletion, you are prompted as
to whether the caller's name should be added to the
JOKER.DAT file.
Command <M> - Change Msg Data
Upon choosing this option, the following menu appears:
<N>umber Of Msgs, <C>onference, <Q>uit?
<N>umber of Msgs allows you to modify the number of
messages entered by the caller. This must be a
numeric value ranging from 0-9999.
<C>onference allows you to change the caller's last
message conference number.
<Q>uit returns you to the SPITFIRE User Record Menu.
Command <P> - Caller Password
Provides an opportunity to view or change the caller's
password. When selected, you will be prompted with:
<V>iew, <C>hange, <Q>uit. If V is selected, the
caller's password is displayed. If C is selected,
a new password can be entered for the caller. SPITFIRE
Page 66
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
allows up to 14 characters for the input of the new
password. Once the new password is entered, it will be
redisplayed and you will be prompted to verify that the
information is correct. If <Q> is selected, the screen
with the caller information is again displayed.
Command <L> - Lock Caller Out
Toggles whether a caller is locked out from the BBS. Any
caller who is locked out will be denied access to the BBS
when he/she attempts to log on. Notice that when a
caller is locked out, the words "Locked Out!" are
displayed on the menu. When locking out a caller,
SPITFIRE provides the option of adding the caller's name
to JOKER.DAT.
Command <C> - Last File Area
This option will allow you to change the caller's last
file area number. SPITFIRE allows up to 65535 file
areas and you can enter any number from 1 to the number
of the last available file area.
Command <#> - Caller Phone No.
Provides the opportunity for editing the caller's phone
number. Upon selecting this option, you are prompted
to enter the new number. A sample format is also
displayed. The format displayed will depend on how you
have configured the US Phone format option from the
ALT+T configuration window. If the US format is toggled
to Yes, the format will be ###-###-#### and the dashes
will automatically be inserted when entering the new
number. If the US Phone format option is toggled to No,
the format will be [ ] and any 12 character
input will be accepted. Regardless, of the format,
after the new phone number is entered, you will be
asked to verify whether the information is correct.
Command <T> - Times On
This option will allow you to change or edit the number
of times the caller has logged on the BBS. This number
may range from -999 to 9999. Normally you will only
use the range from 1 to 9999 but Sysops or co-Sysops
who do not wish to have their names included in top
caller bulletins may wish to use negative numbers here.
Command <!> - Time Left
This option will allow you to enter the daily time
remaining in minutes. This number may range from
-999 to 9999 minutes remaining.
Page 67
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <R> - Record Number
This option will allow you to enter a specific caller
record number. Upon entering the number, all current
information for the record number you specified will
be displayed.
Command <E> - Enter Subscription Date
This option allows the Subscription Date to be edited.
This option is included for Sysops who require callers
to subscribe in order to gain access to their system.
SPITFIRE's default setting is "N/A". If a Sysop wishes
to use this option, the subscription date will need to
be set. In the event, the Sysop decides to change the
Subscription Date back to "N/A", this can be done by
entering 01-01-80 as the Subscription Date.
Command <$> - More Prompt
Selecting the "$" More Prompt option from the command
line will toggle the More Prompt On and Off. If the More
Prompt is toggled On, each time a complete screen display
is received the "More, Continue" prompt is sent and the
display is paused until a keystroke is entered signaling
the display to continue. The number of lines of text
which are displayed between the "More, Continue" prompt
is determined by the caller's screen display setting set
from <Y>our Statistics of SPITFIRE's Main Menu. For
instance, if the screen display is set at 80X23, after
every 23 lines the "More, Continue" prompt will be
displayed. If the More Prompt is toggled Off, the "More,
Continue" prompt will not display and information will
continue to scroll without being paused.
Command <F> - Find Caller
When this option is chosen you are prompted to input the
full or partial name of the caller you are attempting to
find. SPITFIRE will search for any string matching what
was entered. When a match is found, SPITFIRE will report
the find and prompt you as to whether this is the caller
you were searching for. If you respond with a Y for Yes,
SPITFIRE will display that caller's record information.
If you respond with an N for No, SPITFIRE will continue
to search the caller data base, informing you of any
match found, prompting whether the match is the caller
you are searching for. In the event, no match is found,
SPITFIRE will inform you no match could be found.
***NOTE*** When inputting your search criteria you will
notice that SPITFIRE is not case sensitive.
Page 68
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <S> - Security Level
Provides an opportunity to edit the security level of
the current caller record. You will be prompted to
enter the caller's new security level when this option
is selected. SPITFIRE allows up to a four digit figure
for the new security level and will only accept numeric
values.
Command <B> - Birth Date
Provides the opportunity to edit the caller's birth date.
When selected, you are prompted to enter the new birth
date. The format for entering the correction is the
numerical representation for MM-DD-YY. SPITFIRE will
automatically insert the dash between the month, the
day and the year. Once the corrections have been made,
SPITFIRE will prompt you by displaying the new birth date
entered and ask you to verify if the changes are correct.
Command <O> - Original Log Date
Provides the opportunity to change or edit the date the
caller logged onto the BBS for the first time (original
date). When selected, you are prompted to enter the new
date of the original log on. The format for entering the
correction is the numerical representation for MM-DD-YY.
SPITFIRE will automatically insert the hyphens between
the month, the day and the year. Once the corrections
have been made, SPITFIRE will prompt you by displaying
the new date entered and ask you to verify that these
changes are correct.
Command <@> - Add New Caller
This option provides you the opportunity to add a new
caller to the SFUSERS.DAT. Adding a new caller locally,
eliminates the necessity of the new caller responding
to the new caller questionnaire when calling the BBS for
the first time.
You will be prompted to provide certain information about
the caller before they can be added. You will need to
answer prompts regarding the caller's name, address,
password, birthdate (if required on your BBS) and phone
number. Once this information is entered, you will be
prompted for the security level you wish to assign to the
new caller. The security level you assign will determine
what features of the BBS the new caller will have access
to.
Page 69
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <Z> - Purge Allowed
This option allows you to toggle whether purging the
caller will be Allowed or Not Allowed. Normally, you
will want this toggled to Yes. If set to allow the purge
and the caller has not logged on the BBS for the number
of days configured by the Sysop, when packing the callers
file, the caller will be deleted. However, if toggled to
not allow the purge, the caller will not be deleted from
the caller's data base file during packing regardless of
how many days it has been since the caller last logged
on SPITFIRE default to Yes.
<O> ALT+C (Enter/Exit Chat Mode)
----------------------------------
This feature is for entering and exiting chat with a caller. You
can use this feature to answer a page or force a caller into chat.
When you answer a page, the caller's time on-line continues to be
reduced. However, when you force a caller into chat, the caller's
time on-line counter is halted until the chat is finished and the
caller is returned to the system.
<R> ALT+D (Jump to DOS - Off Hook)
------------------------------------
This feature allows you to jump to DOS at the "Ready..." prompt
and places the modem offhook so callers attempting to phone the
BBS will get a busy signal. When you wish to go back to SPITFIRE,
type EXIT. If you are not in the proper directory when you EXIT,
SPITFIRE will automatically take you back to the directory in
which SPITFIRE resides.
<R> ALT+E (Configure Events)
------------------------------
This feature causes the Events Menu to be displayed. The Events
Menu is used to cycle through the active events in a forward or
backward direction, list events, enable an event or disable an
event. For more information on the ALT+E Events Menu refer to
the section - EVENTS MENU EXPLANATION - of this manual.
<R> ALT+F (Configure File Area Records)
----------------------------------------
While SPITFIRE is at the "SPITFIRE ready for use.." prompt, you
can select ALT+F to configure your File Area system records. This
feature allows you to do so without having to go through the
motions of logging on as Sysop and using the Sysop Menu to make
these changes. Refer to the section - CONFIGURING FILE AREA
RECORDS - of this manual for more detailed information .
<B> ALT+J (Jump to DOS - On Hook)
-----------------------------------
Page 70
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
This feature allows you to jump to DOS when a caller is on-line
and also when you are at the "Ready..." prompt. When you wish to
go back to SPITFIRE, type EXIT. If you are not in the proper
directory when you EXIT, SPITFIRE will automatically take you back
to the directory in which SPITFIRE resides. ALT+J does not set
the modem offhook.
<O> ALT+L (Lock Caller Off System)
-----------------------------------
ALT+L can be utilized to lock a caller out of your BBS while they
are on-line. Once the ALT+L is pressed to lock the caller out,
the Sysop is prompted as to whether the caller should be locked
out. If the Sysop responds with a "Y" for Yes, the Sysop is then
asked if the caller should be logged off. If ALT+L is pressed a
second time, SPITFIRE displays a message informing you the caller
is locked out and prompts you as to whether you wish to reverse
the lockout. In other words, the ALT+L is used to toggle whether
a caller is to be locked out from the BBS.
<R> ALT+M (Configure Modem)
-----------------------------
This feature sets the modem off hook and allows you to configure
your modem initialization string, COMM port, baud rate, etc. You
will also notice a toggle switch for use with an error correction
modem. If you are using an error correction modem, be sure to
turn this switch ON and enter the Error Correction Message
specific to your modem type.
If you are using an error correction modem and this is not done,
when a caller logs on with an error correction modem, the Ymodem-g
transfer protocols will not be available to the caller. (Refer to
the section - GETTING STARTED - of this manual for detailed
information.)
In the event your modem requires an initialization string
different than those listed in this manual, please forward the
information to Buffalo Creek's BBS (515-225-8496), so that the
information can be passed on to other Sysops.
<R> ALT+P (Configure File Paths)
---------------------------------
Pressing the ALT+P at the "SPITFIRE ready for use..." prompt
sets the modem off hook and opens a window which allows you to
configure the File Paths. (For more information on this, refer to
the section - GETTING STARTED and the section - FILE PATHS of this
manual.)
<R> ALT+Q (Sysop Quick Log-On/Sysop Next)
-------------------------------------------
Page 71
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
This feature is used to log on SPITFIRE locally. It can be used
at the "Ready..." prompt or while a caller is on-line. Logging on
with ALT+Q will not display the initial log on display files, but
rather takes you right to the Main Menu after entering your
name and password.
<R> ALT+R (Configure Msg Conferences)
---------------------------------------
While SPITFIRE is at the "SPITFIRE ready for use.." prompt, you
can select ALT+R to configure your Message Conference records.
This feature sets the modem off hook and allows you to configure
your Message Conferences without having to go through the motions
of logging on and using the Sysop Menu to make these changes.
Refer to the section - CONFIGURING MESSAGE CONFERENCE RECORDS - of
this manual for detailed information.
<B> ALT+S (Log On Locally/Sysop Next)
--------------------------------------
This feature is used to log on to SPITFIRE locally. It can be
used at the "Ready..." prompt or while a caller is on-line. If
you use this feature while a caller is on-line, then when the
caller logs off, SPITFIRE will sound a audible signal to notify
you the BBS is now available. You will then be able to log on
immediately. Logging on with ALT+S will display all the initial
display files available on the system, such as SFPRELOG.BBS,
WELCOME1.BBS/CLR, through WELCOME9.BBS/CLR and ALL.BBS/CLR.
<R> ALT+T (Toggle SPITFIRE Switches)
--------------------------------------
This feature sets the modem off hook and allows you to set the
various toggle switches contained within SPITFIRE. (For more
information on this, refer to the section - GETTING STARTED - of
this manual.)
<R> ALT+Z (Configure SPITFIRE)
--------------------------------
This feature sets the modem off hook and allows you to configure
certain aspects of SPITFIRE. (Refer to the section - GETTING
STARTED - of this manual for detailed information.)
<B> HOME (SPITFIRE Sysop Help Screen)
---------------------------------------
The "HOME" key displays a quick summary of all the special
function keys available to the Sysop. When used at the SPITFIRE
"Ready..." prompt a window will open up displaying the help
information. When used while a caller is on-line and if the
Sysop is using the divided/split screen option, the upper portion
of the screen will display the help information.
Page 72
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
9.0 MAIN SECTION EXPLAINED
---------------------------
The Main Menu is the crux of any system, as all other sections
of the BBS may be accessed from the Main Menu. However, it is
important to note that a caller does not have to return to the Main
Menu from the Message Section to go to the File Section (and vice-
versa). In the event there is a command on the Main Menu that you do
not wish to have functional, set the security level of that command
high enough so callers cannot access it or see it.
As the Main Menu is described and the features explained, please
keep in mind that you control which callers can access these features
by changing the security level of the commands. In other words, you
control which commands are available to which callers. (For instance
if the security level of the <B>.... Bulletins command is set at 25
then a caller with a security level of 24 or less would not see the
command or be able to use the command.)
The Main Menu is the first focal point your callers will see after
they have gone through the log on screens. For the purpose of
discussion, each menu displayed will be as if the Sysop (with the
highest security level) were viewing it. In this case the Main Menu
would look like this:
9.1 MAIN MENU EXAMPLE
----------------------
>>>>>>>>> MAIN MENU <<<<<<<<<
<M>.......... Message Section <F>.............. File Section
<S>........... SPITFIRE Doors <B>................. Bulletins
<C>......... Comment To Sysop <#>....... List Active Callers
<L>.......... Locate A Caller *<W>............ Welcome Screen
<Q>....... Questionnaire Menu <T>........ This System's Info
<N>............... Newsletter <P>............ Page The Sysop
<G>........ Goodbye & Log Off <X>......... Xpert Mode Toggle
<Y>.......... Your Statistics <O>..... Other Bulletin Boards
<A>......... Add BBS Name & # <K>....... Main Menu Extension
<@>.......... Sysop Utilities <?>........ HELP With Commands
MAIN MENU - <M F S B C # L W Q T N P G X Y O A K @ ?>?
* The <W>... Welcome Screen is used for single node SPITFIRE BBS
system only. If you are operating a multi-node SPITFIRE BBS,
this is replaced with <W>........ Who's On/Node Chat.
Page 73
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
9.2 EXPLANATION OF MAIN MENU FEATURES
--------------------------------------
<M>.... Message Section
This feature takes a caller from the MAIN Section of SPITFIRE
to the MESSAGE Section.
<F>.... Files Section
This feature takes a caller from the MAIN Section of SPITFIRE
to the FILE Section.
<S>.... SPITFIRE Doors
This feature allows a caller to terminate SPITFIRE so a
third party program can be run on-line. Normally, but not
always, the third party program is a game. When the third
party program is finished, the caller is returned to
SPITFIRE.
<B>.... Bulletins
This feature allows a caller to view the available bulletins.
<C>.... Comment to Sysop
Allows a caller to enter a non-public message to the Sysop.
All comments are automatically saved to Message Conference
#1. However, these are marked and listed as Comment Number
<x> rather than Message Number <x>. In order for callers to
leave a comment to the Sysop, the Sysop must log onto the
BBS using the name configured as the Sysop Caller Name in the
ALT+Z configuration window. If the Sysop does not use the
name entered there for logging onto the BBS, callers will
not be able to leave a comment to the Sysop.
<#>.... List Active Callers
This feature displays the name and address of each caller
of this BBS. It also shows the date each caller last logged
on.
<L>.... Locate a Caller
This feature allows a caller to see if a another person is a
caller on this BBS. When a caller selects this feature, the
caller is prompted to enter either the full or partial name
of the person he/she is attempting to locate. SPITFIRE will
search for any string matching what is entered. When a
match is found, SPITFIRE will report the find and ask the
caller as to whether this is the person he/she is attempting
to locate. If the caller responds with a Y for Yes, SPITFIRE
will notify the caller when that person last logged onto the
BBS. If the caller responds with an N for No, SPITFIRE will
continue to search the caller data base, informing the caller
Page 74
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
of any match found, prompting whether the match is the person
they are attempting to locate. In the event no match is
found, SPITFIRE will inform the caller no match could be
found.
<W>.... Welcome Screen (Single Node SPITFIRE BBS)
This feature allows a caller to review the opening screen.
This feature is only available on single node SPITFIRE BBS
systems. On multi-node SPITFIRE systems this option is
replaced with <W>........ Who's On/Node Chat.
<W>.... Who's On/Node Chat (Multi-node SPITFIRE BBS)
This feature will display information regarding what other
callers are currently logged on the other available nodes
and provide an option for entering into a node chat with a
caller on another node. (Refer to the section - NODE CHAT
for a more detailed explanation of node chat). This feature
is only available on multi-node SPITFIRE BBS systems. On
single node SPITFIRE systems this option is replaced with the
<W>...Welcome Screen.
<Q>.... Questionnaire Menu
This feature presents the Questionnaire Menu to your callers.
Individual questionnaire/order files (SFORDER<x>.QUE) are
used to present questions to your callers. The caller's
responses are then stored in the corresponding answer file,
SFORDER<x>.REP. (For more information, please refer to the
section, SPITFIRE Questionnaires of this manual.)
<T>.... This System's Info
This feature displays to the caller certain information about
the BBS, such as the Sysop's name, starting date of the BBS,
total number of calls received on the BBS, etc.
<N>.... Newsletter
This feature displays SFNWSLTR.BBS/CLR (the BBS newsletter)
to the caller. This can be used to keep the callers updated
with changes or news concerning your BBS.
<P>.... Page the Sysop
This feature notifies the Sysop that a caller has a question
or problem to chat about. If the Sysop is not available to
answer the page, SFUNANS.BBS/CLR is displayed to the caller.
If a caller attempts to page the Sysop a second time, and
SFPAGED.BBS/CLR is found, SFPAGED.BBS/CLR is displayed to
the caller and the Sysop is not paged a second time. If
SFPAGED.BBS/CLR is not found, the caller may page the Sysop
multiple times. If the Sysop has the page feature turned
off and a caller attempts to page the Sysop, SFPGOFF.BBS/CLR
is displayed to the caller.
Page 75
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<G>.... Goodbye & Log Off
This feature simply allows a caller to log off the BBS.
<X>.... Xpert Mode Toggle
This feature changes a caller's status from a novice to an
expert or vice versa. If a caller is set as a novice, then
the menu descriptions will scroll by after each command. If
a caller is set as an expert, then only the command letters
scroll by after each command.
<Y>.... Your Statistics
This feature displays certain statistics for the caller on
the BBS and provides a menu which gives the caller the
opportunity to change some information pertaining to them.
The screen and the information that can be changed are
explained below:
>>>>>> JUST FOR YOUR INFORMATION <<<<<<
Your Name : John Doe Security Level : 10
Last Time On : 03-20-92 13:04 Number Of Times On : 127
Birthdate : 01-20-54 Times On Today : 1
Files Uploaded : 19 Files Downloaded : 53
K Uploaded : 122 K Downloaded : 2631
Original Log On : 05-23-90 Subscription Date : N/A
Node Chats Left : 5 Messages Entered : 22
>>>>>>>> THINGS YOU CAN CHANGE <<<<<<<<
<W> Address : Peoria, IL <H> Hot Key : On
<#> Phone Number : 555-151-5555 <D> Display Size : 80X24
<S> Scroll Prompt : On <A> ANSI On/Off : On
<F> File Transfer : 1k-Xmodem <M> More Prompt : On
<P> Password : SPITFIRE <C> Change Color : 36
CHANGE MENU - [W S # H C A D M P F <Q>uit ] ?
Command <W> - Provides the caller with an opportunity to change their
address. The caller is prompted to enter both the city
and state. SPITFIRE will then redisplay what they have
entered to verify the changes before saving the new
information.
Command <S> - Allows the caller to toggle SPITFIRE's Scroll Back
option On and Off. The scroll back feature is used in
connection with the display of the "< ENTER >"/"More,
Continue" prompts. If the scroll back feature is toggled
on, when the prompt is displayed and the caller enters a
keystroke to continue, the message will scroll back and
disappear from the screen. If the scroll back feature is
off, the "< ENTER >" or "More, Continue" prompt remains
displayed on the screen.
Page 76
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Command <#> - Allows the caller to change their phone number.
Command <H> - This feature allows the caller to toggle the Hot Key
within SPITFIRE. If toggled On, when entering the
command character of a menu, a return is entered
automatically and the command is immediately executed.
When toggled off, the caller is required to press the
<ENTER> key before the command is executed.
Command <C> - Allows the caller to select their default color settings.
The caller may select 31 through 36. The colors
associated with the numeric value are as follows:
31 - Red 32 - Green 33 - Yellow 34 - Blue
35 - Magenta 36 - Cyan 37 - White
Command <A> - Allows the caller to toggle ANSI color on and off.
Command <D> - Allows the caller to set the screen display size. When
this feature is selected, the caller is prompted to
enter a new line length. Acceptable values for the
line length range from 40 to 144. Next, the caller
is prompted to enter a new page length. Acceptable
values for the page length range from 10 to 24. The
page length determines when the "More, Continue" prompt
will display. For example, if the page length is 24,
the prompt will display after every 24 lines.
Command <M> - This toggles the More Prompt On and Off. When toggled
On, each time a complete screen display is received,
either the "< ENTER >" or "More, Continue" prompt is sent
and the display is paused until a keystroke is entered
signaling the display to continue. If the More Prompt is
toggled Off, the "< ENTER >"/"More, Continue" prompt will
not display and information will continue to scroll
without being paused.
Command <P> - Allow the caller the opportunity to change their log on
password.
Command <F> - Allow the caller to select their default file transfer
protocol. The caller may select from:
<1> Ascii
<2> Xmodem Checksum
<3> Xmodem CRC
<4> 1k-Xmodem
<5> SEAlink Derived
<T> Telink
<S> Select at time of transfer
Page 77
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Selecting any option other than <S>, Select at time of
transfer, causes the external protocol options to be
unavailable to the caller. SFPROMSG.BBS/CLR is used
to inform the caller of this when selecting a default
file transfer.
Command <Q> - Returns the caller to the Main Menu
<O>.... Other Bulletin Boards
This feature displays SFBBSLST.DAT which is a listing of
names, bps rate and phone numbers of other Bulletin Boards.
<A>.... Add BBS Name & #
This feature allows a caller to add the name, bps rate and
phone number of other bulletin board systems to the BBS list,
SFBBSLST.DAT. When adding a BBS to SFBBSLST.DAT, the number
is recorded in the caller's log to provide the Sysop a means
of tracing who entered the listing.
<K>.... Main Menu Extension
This command can be set to run a third party program
configured by the Sysop. It is set up using the necessary
commands to execute the desired option within the SFMAIN.BAT
file. It should be noted that Sysops will need to use the
SFHELP.EXE utility to modify the SPITFIRE.HLP file so it
properly explains the added option.
<@>.... Sysop Utilities
This feature takes a caller from the MAIN Section to the
SYSOP section. The BBS is maintained from the SYSOP Section.
This feature is not normally available to most callers.
<?>.... HELP with Commands
This feature will provide help for each command available
from the MAIN MENU.
10.0 MESSAGE SECTION EXPLAINED
-------------------------------
The Message Menu is the point from which your callers take part
in mail exchange. The Message Menu may be selected from either the
Main Menu or the File Menu with the <M>...Message Section command
option.
As the Message Menu is described and the features explained,
please keep in mind that you can control the usage of each command by
changing the security level of the commands. In other words, you can
control what commands are available to what callers. For the purpose
Page 78
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
of discussion, however, each menu displayed will be as if the Sysop
(with the highest security level) is viewing it. In this case the
Message Menu would look like this.
10.1 MESSAGE MENU EXAMPLE
--------------------------
>>>>>>>> MESSAGE MENU <<<<<<<<
<L>.. LAKOTA (QWK) Mail System <C>. Change Message Conference
<R>............. Read Messages <H>....... Hurry Scan Messages
<B>........... Browse Messages <N>.. Non-stop Message Capture
<E>........... Enter A Message <Y>............. Your Messages
<A>........Alter Message Queue <T>............... Text Search
<F>.............. File Section <P>............ Page The Sysop
<Q>......... Quit To MAIN MENU <G>......... Goodbye & Log Off
<X>......... Xpert Mode Toggle <K>.... Message Menu Extension
<@>........... Sysop Utilities <?>........ HELP With Commands
MESSAGE MENU - <S C R H B N E Y A T F P Q G X K @ ?>?
10.2 MESSAGE MENU EXPLANATION
------------------------------
<L>.... LAKOTA (QWK) Mail System
When this option is selected, SPITFIRE shells to LAKOTA.COM,
SPITFIRE's Mail System and the following menu is displayed:
<D>............. Download Messages (QWK Format)
<U>............... Upload Messages (QWK Format)
<S>............. Set Last Read Message Pointers
<Q>....................................... Quit
Selecting <D> displays the Download Message Menu:
>>>> Download Message Menu <<<<
<N>............... New Messages
<T>..................... To You
<Q>....................... Quit
This menu defines the selection criteria of the messages
to be downloaded using SPITFIRE's Mail System. Once the
caller chooses between downloading new messages or messages
addressed to them, the conference menu is displayed:
>>>> Message Conference Menu <<<<
<A>.............. All Conferences
<B>.......... Select A Conference
<C>...... Your Queued Conferences
<Q>......................... Quit
Page 79
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
This menu allows the caller to define what
conferences messages will be extracted from
during the message download process.
The caller is then asked whether the last message read
pointers should be updated.
If the caller is logged on locally the message packet will
be placed in SPITFIRE's home directory. If the caller is
logged on remotely a menu will display from which the caller
can select the file transfer protocol to be used for the
message download.
Selecting <U> from SPITFIRE's Mail System Menu allows the
caller to upload replies in QWK format which are imported
into SPITFIRE's message base. Prior to the upload, LAKOTA
verifies that the amount of available disk space is greater
than that which the Sysop has configured at the ALT+Z Upload
Disk Space Requirement option.
If the caller is logged on locally, the following prompt
appears:
File must be in .ZIP format!
Enter name of the file to import:
The first character entered should be the drive letter where
the file to be uploaded is located. LAKOTA automatically
inserts the semi-colon and the backslash after this letter is
entered. (In other words, if you input the letter C, LAKOTA
will place the :\ after this character to make it "C:\".)
Next enter the path and name of the file to be imported.
LAKOTA will import messages from the reply file directly into
SPITFIRE's message base.
If the caller is logged on remotely a menu will display from
which the caller can select the file transfer protocol to be
used to upload the message reply packet. Once the file is
received, it is imported into the SPITFIRE message base.
Selecting <Q> returns the caller to SPITFIRE Message Menu.
For more information on LAKOTA, SPITFIRE's QWK Mail System,
refer to the documentation, LAKOTA.DOC.
<C>.... Change Message Conference
This feature allows a caller to change to a different Message
Conference by entering the number of the Message Conference
he/she wishes to change to. If a caller selects <Q>uit, the
Page 80
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
caller will remain in the current Message Conference. If a
caller presses the ENTER key, SPITFIRE will list the Message
Conferences available to the caller. If a MGLST<x>.BBS/CLR
is found it will be displayed here. After changing to a new
message conference, SPITFIRE will prompt the caller as to
whether he/she would like to read messages in the conference
they have changed to.
<R>.... Read Messages
This feature allows the caller to read public messages and
non-public messages sent to and/or from the caller in the
specified Message Conferences. The caller is presented with
five options and may elect to read:
<T>...This Message Conference
This option allows the caller to read available
messages in the current Message Conference.
<A>...All Message Conferences
This option allows the caller to read available
messages in all Message Conferences to which the
caller has access.
<O>...Only Queued Conferences
This option allows the callers to read available
messages in the Message Conferences the callers have
selected to be included in their Message Queue.
<S>...Set Conference Queue
When this option is selected, SPITFIRE will display
a list of all conferences contained in the caller's
message queue and prompt the caller as to whether to
change the current queue. If the caller selects to
change the queued message conferences, the Message
Queue Menu is displayed. For more information on
the Message Queue Menu, refer to Command <A>..Alter
Message Queue discussed below.
<Q>...Quit
This option will return the caller to the Message Menu.
During the process of reading messages, the caller will have
the following commands available to them, provided the
command is a viable option at the time. If it is not a
viable option, the command will not be shown to the caller.
<R>...Reply
Allows the caller to reply to an existing message.
When replying to a message, SPITFIRE will prompt the
Page 81
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
caller as to whether they wish to change the message
subject. If the caller responds with a "Y", the caller
is given the opportunity to change the message subject.
If the caller responds with a "N", the message subject
remains the same as the original message. Replies to
messages with the same message subject allows the
messages to be threaded together. The caller is also
prompted as to whether the reply should be made public
if the Message Conference allows non-public messages.
If the caller is replying to a message in a conference
which allows non-public messages the caller will be
prompted as to whether the reply should be public
or non-public. SPITFIRE will default to how the
original message was entered. In other words, if the
original message was public, SPITFIRE defaults to
making the reply public. When the prompt is displayed
the caller may override the default or simply hit Enter
to accept the default.
When replying to a message the caller may use the
combination CTRL+Q keys to Review/Quote Original
Message. The original message is redisplayed and
the caller is prompted to enter the line numbers
for the range of lines which he/she desires to quote.
This range is then included in their reply message
with the initials from the author of the original
message preceding each line. For example:
MW> SPITFIRE is the best BBS software available!
A quoted portion of a reply cannot be edited.
If the person replying to the message is logged on
locally, another option, the CTRL+F will allow an
existing text file to be imported into the reply.
When the CTRL+F - Import File! feature is selected,
SPITFIRE will prompt you for the path and file name
of the file to be imported. In the event a file name
is not entered, SPITFIRE will look in the Work
directory for a file named SFMSG.TXT and import this
if it is found. If after pressing the CTRL+F keys
you decide you do not want to import a file, simply
enter a non-existent path at the prompt to abort the
process.
Page 82
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<D>...Delete
This option will be available only if 1) the caller
has Sysop security or 2) the Message Conference has
been configured to allow the caller the ability to
delete messages and the message is either being sent
to by the caller. Deleting a message makes it
unavailable except to those with Sysop security and
will cause it to be purged from the message base the
next time the message base is packed.
<N>...Non-stop
This feature will display all appropriate messages
nonstop.
<E>...Enter A Message
This feature allows a caller to enter a message. If
the message the caller enters is not addressed to a
specific person, then SPITFIRE addresses the message to
"All Callers". When addressing a message to a specific
person in a message conference that has not been
configured as a net-mail conference and that person is
not found in caller's data base, SPITFIRE notifies the
caller that the person to whom the message is addressed
could not be found and prompts the caller with "Try
Again? [Y/n]". This allows the caller to re-enter the
name of the person for whom the message is intended or
to abort the message. SPITFIRE will not allow a caller
to enter messages addressed to a specific person if
that person cannot be found in the caller's data base
unless the Message Conference in which the message is
being entered is configured as a net-mail conference
and the message is marked to be sent via net-mail.
When entering a message in a net-mail conference, you
will be prompted as to whether to send the message via
net-mail. If the message conference is configured to
allow Caller Message Deletion a second prompt will
appear regarding whether the message should be purged
when sent. If the caller responds with a Y, once the
message is sent it will be purged the next time the
message conference is packed. If the conference is
configured to allow Message Routing, the caller is also
prompted as to whether the message should be routed.
If the caller responds with a Y, he/she will then be
asked to enter the routing number or name. If the BBS
is using BCSUTI the message is automatically routed to
the specified destination. Other UTI programs may
require the message to be routed in the normal fashion.
Page 83
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Callers are allowed to send carbon copies of a message
to other callers. SPITFIRE allows a total of nine
carbon copies per message and automatically prevents
duplicating carbon copy messages to callers already
receiving the message. Using carbon copies in
conjunction with the routing feature will allow the
caller to send the same message to ten different
callers, routing it to ten different locations.
SPITFIRE allows a total of 99 lines per message but
the Sysop can configure, per message conference, the
maximum number of lines per message that will be
allowed. When entering (or responding) to a message,
SPITFIRE can display the Message Conferences available
to the caller and whether the specified Message
Conference allows public or public and non-public
messages. Pressing ENTER twice when prompted for the
message subject will abort the message.
When logged on locally and entering a message, another
option, the CTRL+F will allow an existing text file to
be imported into the reply. When the CTRL+F - Import
File! feature is selected, SPITFIRE will prompt the
caller for the path and file name of the file to be
imported. In the event, a file name is not entered,
SPITFIRE will look in the Work directory for a file
named SFMSG.TXT and import this if it is found. If
after pressing the CTRL+F keys you decide you do not
want to import a file, simply enter a non-existent
path at the prompt to abort the process.
<ENTER>...Next Message
Pressing the enter key will cycle the caller to the
next available message to be read.
<->...Previous Message
Allows the caller to return to the previous message
in the current conference.
<#>...Number Of An Existing Message In This Conference
Entering a number of a specific message that is
available in the conference will display that message.
<F>...Follow Msg Thread
Allows the caller to simultaneously read messages
which are threaded together by a common Message
Subject. When this option is selected the following
menu is displayed:
Page 84
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
>>>> MESSAGE THREAD MENU <<<<
<S>........ Start Of Thread
<F>........... Forward Read
<B>.......... Backward Read
<E>.... Exit Message Thread
<S>...Start Of Thread will take the caller to the first
message containing the common message subject
which threads the messages together.
<F>...Forward Read will cycle through the threaded
messages in forward order one message at a time.
<B>...Backward Read will cycle through the threaded
messages in reverse order one message at a time.
<E>...Exit Message Thread will return the caller to the
original message from where the Threaded Message
Menu was activated.
<P>...Public
Allows a caller with Sysop security to toggle a public
message to non-public or to toggle a non-public message
to public.
<U>...Undelete
Allows a caller with Sysop security to undelete a
deleted message, making it available once again.
<X>...Xport
This feature is only available when a caller is logged
on locally. When selected, SPITFIRE checks to see if
a printer is attached and ready for printing. If so,
SPITFIRE provides the option of exporting the message
to the printer or saving it to a text file on disk.
If no printer is attached or it is not ready for
printing, the message is saved as a text file in the
directory designated as the Message file path. The
format for the file name it is saved to is:
MSG+message#.conference#. In other words, if
message number 15 in conference 3 was Xported, it
would be saved as MSG15.3.
<C>...Copy
This feature is only available to a caller with Sysop
security. This feature actually serves two purposes.
First, it allows the caller to move the message to
another message conference. SPITFIRE will inform the
caller to whom the message is currently addressed and
Page 85
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
prompt if this should be changed, thus, also allowing
the message to be forwarded to another caller. When
copying a message to a conference that is configured
as a net-mail conference, the caller is prompted as to
whether the message should be marked as a net-mail
message and if so, whether the message should be purged
when sent.
<Q>...Quit
Returns the caller to the Message Menu.
<H>.... Hurry Scan Messages
This feature allows a caller to scan messages in a specific
Message Conference or in all Message Conferences. This scan
doesn't provide as much information regarding the messages
as the <B>rowse Messages feature.
<B>.... Browse Messages
This feature allows a caller to scan messages in a specific
Message Conference or in all Message Conferences. This
scan provides the caller with more information regarding the
messages than the <H>urry Scan Messages feature.
<N>.... Non-stop Message Capture
When this feature is executed, SPITFIRE will display all
appropriate messages non-stop. The caller normally uses
some means to capture the messages for later reading or
printing.
<E>.... Enter A Message
This feature allows a caller to enter a message. If the
message the caller enters is not addressed to a specific
person, then SPITFIRE addresses the message to "All Callers".
When addressing a message to a specific person in a message
conference that has not been configured as a net-mail
conference and that person is not found in caller's data
base, SPITFIRE notifies the caller that the person to whom
the message was addressed could not be found and prompts the
caller with "Try Again? [Y/n]". This allows the caller to
re-enter the name of the person to whom the message was
addressed or to abort the message. SPITFIRE will not allow
callers to enter messages addressed to a specific person if
that person cannot be found in the caller's data base unless
the Message Conference in which the message is being entered
is configured as a net-mail conference and the message is
marked to be sent via net-mail.
When entering a message in a net-mail conference, you will be
prompted as to whether to send the message via net-mail. If
Page 86
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
the message conference is configured to allow Caller Message
Deletion a second prompt will appear in regard to whether
the message should be purged when sent. If the caller
responds with a Y, once the message has been sent it will be
purged the next time the message conference is packed. If
the conference is configured to allow Message Routing, the
caller is also prompted as to whether the message should be
routed. If the caller responds with a Y, he/she will be
asked to enter the routing number or name. If the BBS is
using BCSUTI the message is automatically routed to the
specified destination. Other UTI programs may require
the message to be routed in the normal fashion.
Callers are allowed to send carbon copies of a message to
other callers. There are a total of nine carbon copies
available. SPITFIRE will automatically prevent duplicating
carbon copy messages to callers already receiving the message.
Using the carbon copies in conjunction with the routing
feature will allow the caller to send the same message to nine
different callers, routing it to nine different locations.
SPITFIRE allows a total of 99 lines per message but the Sysop
can configure, per message conference, the maximum number of
lines per message that will be allowed. When entering (or
responding) to a message, SPITFIRE will display the Message
Conferences available to the caller and whether the specific
Message Conference allows public or public and non-public
messages. Pressing ENTER twice when prompted for the message
subject will abort the message.
If the person entering the message is logged on locally,
another option, the CTRL+F will allow an existing text file
to be imported into the reply. When the CTRL+F - Import
File! feature is selected, SPITFIRE will prompt the caller
for the path and file name of the file to be imported. In the
event, a file name is not entered, SPITFIRE will look in the
Work directory for a file named SFMSG.TXT and import this if
it is found. If after pressing the CTRL+F keys you decide
you do not want to import a file, simply enter a non-existent
path at the prompt to abort the process.
<Y>.... Your Messages
This feature will display the caller's message statistics.
The caller receives a report on the number of new messages
they have waiting to be read, the number of messages they
have already received, the number of messages the caller
has sent and the total number of messages available on
the BBS. The caller is then prompted if they would like
to read their messages.
Page 87
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
*NOTE* If the caller is recognized as the Sysop of the BBS, he/she
will also be prompted as to whether he/she would like to
preview messages. If the Sysop replies with a Yes, SPITFIRE
allows you to read your messages, but does not mark them
as being received. (For more information on the Message
Preview feature, refer to section SPECIAL COMMANDS FOR
SYSOP of this manual.)
<A>.... Alter Message Queue
This feature allows a caller to include specific message
conferences in his/her message conference queue. Conferences
not included in the caller's message queue will be ignored.
When a caller selects the <A>...Alter Message Queue option,
the caller is presented with the following sub-menu:
>>>> MESSAGE QUEUE MENU <<<<
<A>...... Add A Conference <C>....... Current Queue List
<D>... Delete A Conference <I>.. Include All Conferences
<L>.. List Msg Conferences <R>... Remove All Conferences
<S>.... Select Conferences <Q>..... Quit To Message Menu
<A>...Add A Conference allows a caller to enter a
specific number corresponding to the Message
Conference number the caller wishes to have added
to their message conference queue.
<D>...Delete A Conference allows a caller to enter a
specific number corresponding to the Message
Conference number the caller wishes to have
deleted from their message conference queue.
<L>...List Msg Conferences will display all message
conferences on the BBS to which the caller
has access.
<S>...Select Conferences will individually display all
message conferences on the BBS to which the
caller has access and prompt the caller as to
whether to include the conference in their
message conference queue.
<C>...Current Queue List will display to the caller the
message conferences currently contained
in their message conference queue.
<I>...Include All Conferences will place all available
message conferences in the caller's message
queue.
Page 88
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<R>...Remove All Conferences will remove all message
conferences from the caller's message queue with
the exception of the first Message Conference.
SPITFIRE requires that all callers have Message
Conference 1 in their queue.
<Q>...Quit To Message Menu will return the caller to
the Message Menu.
** SPECIAL NOTES ABOUT QUEUED CONFERENCES **
Conferences not included in the caller's queue will not be
scanned when SPITFIRE scans for new messages. For this
reason, when a caller attempts to leave a message to another
caller in a message conference that the caller does not have
selected in their queue, SPITFIRE will not allow the caller
to send the message. Also, a caller may delete any message
conference from their message queue, except for the first
message conference. The first message conference will remain
active to all callers.
<T>.... Text Search
This feature allows a caller to search for specific text in a
message. SPITFIRE supports a multi-word text search of up to
6 key words at one time. The text search only searches the
current Message Conference, for messages sent to or from the
caller and public messages. When the text is found in a
message, SPITFIRE will display the message and prompt the
caller as to whether they wish to continue with the search.
<F>.... File Section
This feature takes the caller from the MESSAGE Section of
SPITFIRE to the FILE Section.
<P>.... Page the Sysop
This feature notifies the Sysop that a caller has a question
or problem to chat about. If the Sysop is not available to
answer the page, SFUNANS.BBS/CLR is displayed to the caller.
If a caller attempts to page the Sysop a second time, and
SFPAGED.BBS/CLR is found, SFPAGED.BBS/CLR is displayed to
the caller and the Sysop is not paged a second time. If
SFPAGED.BBS/CLR is not found, the caller may page the Sysop
multiple times. If the Sysop has the page feature turned
off and a caller attempts to page the Sysop, SFPGOFF.BBS/CLR
is displayed to the caller.
<Q>.... Quit To MAIN MENU
This feature takes a caller from the MESSAGE Section of
SPITFIRE to the MAIN Section.
Page 89
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<X>.... Xpert Mode Toggle
This feature changes a caller's status from novice to expert
or vice versa. If a caller is set as a novice, then the menu
descriptions will scroll by after each command. If a caller
is set as expert, then only the command letters scroll by
after each command.
<K>.... Message Menu Extension
This command can be used to run third party programs which
are configured by the Sysop. It is set up by including the
necessary commands to execute the desired option within the
SFMESS.BAT file. It should be noted that Sysops will need
to use the SFHELP.EXE utility to modify the SPITFIRE.HLP
file so it properly explains the added option.
<G>.... Goodbye & Log Off
This feature simply allows a caller to log off the BBS.
<@>.... Sysop Utilities
This feature takes a caller from the MESSAGE Section to the
SYSOP Section. The BBS is maintained from the SYSOP Section.
<?>.... HELP With Commands
This feature will provide help for each command available
from the MESSAGE MENU.
11.0 FILE SECTION EXPLAINED
----------------------------
It is from the File Menu that all file related activity is
accessed. The File Menu may be selected from either the Main
Menu or the Message Menu with the <F>...File Section command option.
The Sysop has the ability to control which features are available to
the callers by adjusting the security level within the SFFILE.MNU
For the purpose of discussion, each menu displayed will be as if the
Sysop (with the highest security level) were viewing it. In this case,
the File Menu would look like this:
Page 90
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
11.1 FILE MENU EXAMPLE
-----------------------
>>>>>>>>> FILE MENU <<<<<<<<<
<C>......... Change File Area <L>.. List Files In This Area
<E>............. Erase A File <G>........ Goodbye & Log Off
<D>.......... Download A File <U>............ Upload A File
<H>.. Help On Upload/Download <P>........... Page The Sysop
<M>.......... Message Section <Q>........ Quit To MAIN MENU
<S>............ Shuffle Files <N>................ New Files
<T>.. Text Search Description <F>.............. Find A File
<X>........ Xpert Mode Toggle <?>....... HELP With Commands
<K>..... File Menu Extension <@>.......... Sysop Utilities
<V>...... View A File Archive <R>......... Read A Text File
FILE MENU - <C L E G D U H P M Q S N T F X ? K @ V R>?
11.2 FILE MENU EXPLANATION
---------------------------
<C>.... Change File Area
This feature allows a caller to change to a different File
Area. If <Q>uit is selected, the caller remains in the
current File Area. If the ENTER key is pressed, SPITFIRE
will list the File Areas available to the caller.
<L>.... List Files In This Area
This displays the files (SFFILES.BBS) in the current
File Area that are available for the caller to download.
When listing files, SPITFIRE offers file tagging for ease
of downloading. SPITFIRE precedes each file in the list
with a tag character. As each screen completes
displaying, the caller is prompted to enter the tag
character(s) associated with a file(s) to be downloaded.
When the file download transfer is begun, SPITFIRE
automatically inserts the name of the file(s) tagged
for downloading.
<E>.... Erase A File
This feature allows callers to erase a file from a File Area.
Normally this feature is only available to callers with Sysop
security. When erasing a file from the file menu, SPITFIRE
prompts you as to whether you wish the file to be added to
SFNOUP.DAT. Responding with a Y for Yes adds the erased
file's name to SFNOUP.DAT. SPITFIRE's file tagging feature
can be used when erasing a file(s). If no files have been
tagged, you must enter the name of the file to be erased.
Before the file is deleted you will be asked to verify that
Page 91
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
the file is to be erased. If files have been tagged for
erasing, the name will default in automatically but SPITFIRE
will still ask you to verify each file before it is erased.
This process will continue until all tagged files are
processed. When erasing a file, information regarding the
file is removed from SFFILES.BBS.
<G>.... Goodbye & Log Off
This feature simply allows a caller to log off the BBS.
<D>.... Download A File
This feature allows a caller to download a file, provided the
caller hasn't exceeded the maximum daily download limit and
the caller has enough time left to perform the download. The
caller does not have to be in any specific File Area to
perform a download. If the caller starts a download while in
a File Area marked as a CD-ROM File Area and the file to be
downloaded isn't found in that area, SPITFIRE asks the caller
whether to search the other File Areas. SPITFIRE allows the
caller to automatically log off after the completion of the
download by placing a backslash "\" after the name of the
file to be downloaded. Upon completing a download, SPITFIRE
notifies the caller of the number of downloads he/she has
remaining for the day.
When the caller is prompted for the name of the file to
download, if the file name and period is input, SPITFIRE
automatically adds the ZIP extension. If, for example,
SF33. is entered, SPITFIRE initiates the download of
SF33.ZIP. If the period is not added, SPITFIRE does
not add the file extension.
Prior to starting the download, SPITFIRE displays to the
caller a list of the files selected for downloaded and the
number of bytes which will be sent.
When the Download A File option is selected by a caller who
is logged on locally, the IMPORT/EXPORT Menu is displayed.
The ANSI/non-ANSI screen for this menu, SFIMPEXP.BBS/CLR,
is displayed if found. Otherwise, the following default
SPITFIRE menu is displayed:
>>>> IMPORT/EXPORT MENU <<<<
<I>...... Import A File <E>............ Export A File
<R>...... Remove A File <T>.. Text Search Description
<F>........ Find A File <L>... List Files (This Area)
<C>... Change File Area <Q>........ Quit To File Menu
<G>... Goodbye & Log Off
ENTER COMMAND <I E R T F L C Q G ?>
Page 92
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<I>... Import A File
Allows a file to be added by copying it from another
drive and/or directory to a SPITFIRE file area.
SPITFIRE prompts the caller to enter the path
name of the file to be copied and also prompts
for a description of the file being copied. The
file name, size, date and description of the file
being copied is added to the SFFILES.BBS for the
file area the file is being copied to.
<E>... Export A File
Allows a file from a SPITFIRE file area to be copied
to a drive and/or directory not set up as a SPITFIRE
file area. The caller is prompted for the name of
the file to be copied and the path to which the
file will be copied to.
<R>... Remove A File
Allows a file to be erased from the SPITFIRE file
area and removed from the appropriate SFFILES.BBS.
When a file is removed, the caller is prompted as
to whether the file should be added to SFNOUP.DAT.
<T>... Text Search Description
Allows a caller to search for certain text within
a file description. The caller can search in a
specific File Area or in all File Areas. This
feature ONLY searches the file description and not
the file name, date or size. However, when the
matching text is located, these are displayed.
<F>... Find A File
Allows a caller to search a specific File Area or
all File Areas for a specific file. Wildcards are
allowed, with the exception of *.*. If a caller
enters a file name without the file extension,
SPITFIRE automatically adds a ".*" to the file name.
If there is a match, the file name, size, date and
description are shown, provided the file is listed
in the SFFILES.BBS.
<L>... List Files (This Area)
Displays the SFFILES.BBS for the current file area,
listing files that are available for the caller to
download. When listing files, SPITFIRE offers file
tagging for ease of downloading. SPITFIRE precedes
each file in the list with an alphanumeric character.
As each screen completes displaying, the caller is
prompted to enter the alpha character(s) associated
Page 93
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
with a file(s) to be downloaded. When the caller
begins the file download process, SPITFIRE will
automatically insert the name of the file(s) the
caller has tagged for downloading.
<C>... Change File Area
Allows a caller to change to a different File Area.
If the caller selects <Q>uit, the caller remains
in the current File Area. If the caller presses the
ENTER key, SPITFIRE lists the File Areas that are
available to the caller.
<Q>... Quit To File Menu
Allows the caller to exit the IMPORT/EXPORT Menu and
return to the File Menu.
<G>... Goodbye & Log Off
Allows the caller to log off the BBS.
<U>.... Upload A File
This feature provides the caller the opportunity to upload
a file. The caller can be compensated additional time on the
BBS for the upload. The amount of the additional time is set
by the Sysop. SPITFIRE allows the caller to automatically
log off after the completion of the upload by placing a
backslash, "\", after the name of the file to be uploaded.
By using a forward slash, "/", at the beginning of the file
description, a caller can upload a file for Sysop only. When
a file is uploaded for Sysop only, it is not added to the
SFFILES.BBS but the Sysop is notified in HEYSYSOP.LOG.
After the name of the file to be uploaded is entered,
SPITFIRE prompts the caller to stand by while it checks to
see if the file already exists. While checking for the file,
SPITFIRE checks for the same file with a different extension.
For example, if a caller attempts to upload SF33.PAK and
SF33.ZIP is found, the caller is notified of the existing
file and is queried as to whether the upload should be
continued. If the Sysop has toggled the Comprehensive Upload
Search to On (ALT+T configuration), during the search,
SPITFIRE removes any trailing digits from the file name. If
a caller attempts to upload SF32.ZIP and SF33.ZIP was found,
the caller is notified of the existing file and queried as to
whether the upload should continue.
When a caller uploads a file which was not expected (no
file name or description was provided by the caller),
at the conclusion of the upload when the file is found
SPITFIRE checks to see if the file already exists. File
Page 94
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Areas with the Search File Area option set to No will not be
searched. If the file is not found, SPITFIRE then prompts
the caller for a description of the file.
When the Upload A File option is selected by a caller who
is logged on locally, the IMPORT/EXPORT Menu is displayed.
The ANSI/non-ANSI screen for this menu, SFIMPEXP.BBS/CLR,
is displayed if found. Otherwise, the following default
SPITFIRE menu is displayed:
>>>> IMPORT/EXPORT MENU <<<<
<I>...... Import A File <E>............ Export A File
<R>...... Remove A File <T>.. Text Search Description
<F>........ Find A File <L>... List Files (This Area)
<C>... Change File Area <Q>........ Quit To File Menu
<G>... Goodbye & Log Off
ENTER COMMAND <I E R T F L C Q G ?>
<I>... Import A File
Allows a file to be added by copying it from another
drive and/or directory to a SPITFIRE file area.
SPITFIRE prompts the caller to enter the path
name of the file to be copied and also prompts
for a description of the file being copied. The
file name, size, date and description of the file
being copied is added to the SFFILES.BBS for the
file area the file is being copied to.
<E>... Export A File
Allows a file from a SPITFIRE file area to be copied
to a drive and/or directory not set up as a SPITFIRE
file area. The caller is prompted for the name of
the file to be copied and the path to which the
file will be copied to.
<R>... Remove A File
Allows a file to be erased from the SPITFIRE file
area and removed from the appropriate SFFILES.BBS.
When a file is removed, the caller is prompted as
to whether the file should be added to SFNOUP.DAT.
<T>... Text Search Description
Allows a caller to search for certain text within
a file description. The caller can search in a
specific File Area or in all File Areas. This
feature ONLY searches the file description and not
the file name, date or size. However, when the
matching text is located, these are displayed.
Page 95
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<F>... Find A File
Allows a caller to search a specific File Area or all
File Areas for a specific file. Wildcards are
allowed, with the exception of *.*. If a caller
enters a file name without the file extension,
SPITFIRE automatically adds a ".*" to the file name.
If there is a match, the file name, size, date and
description are shown, provided the file is listed
in the SFFILES.BBS.
<L>... List Files (This Area)
Displays the SFFILES.BBS for the current file area,
listing files that are available for the caller to
download. When listing files, SPITFIRE offers file
tagging for ease of downloading. SPITFIRE precedes
each file in the list with a tag character. As
each screen completes displaying, the caller is
prompted to enter the tag character(s) associated
with a file(s) to be downloaded. A delimiter between
tag characters is not required. When the caller
begins the file download process, SPITFIRE
automatically inserts the name of the file(s) the
caller has tagged for downloading.
<C>... Change File Area
Allows a caller to change to a different File Area.
If the caller selects <Q>uit, the caller will remain
in the current File Area. If the caller presses the
ENTER key, SPITFIRE lists the File Areas that are
available to the caller.
<Q>... Quit To File Menu
Allows the caller to exit the IMPORT/EXPORT Menu and
return to the File Menu.
<G>... Goodbye & Log Off
Allows the caller to log off the BBS.
<H>.... Help On Upload/Download
This feature describes the various file transfer
protocols available to the caller. The help information
comes from SFPROTCO.HLP and may be edited with your
favorite text editor, provided it saves in ASCII format.
<P>.... Page The Sysop
This feature notifies the Sysop that a caller has a question
or problem to chat about. If the Sysop is not available to
answer the page, SFUNANS.BBS/CLR is displayed to the caller.
If a caller attempts to page the Sysop a second time, and
SFPAGED.BBS/CLR is found, SFPAGED.BBS/CLR is displayed to
Page 96
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
the caller and the Sysop is not paged a second time. If
SFPAGED.BBS/CLR is not found, the caller may page the Sysop
multiple times. If the Sysop has the page feature turned
off and a caller attempts to page the Sysop, SFPGOFF.BBS/CLR
is displayed to the caller.
<M>.... Message Section
This feature takes a caller from the FILE Section of SPITFIRE
to the MESSAGE Section.
<Q>.... Quit To Main Menu
This feature takes a caller from the FILE Section of SPITFIRE
to the MAIN Section.
<S>.... Shuffle Files
This feature allows files to be moved from one file area to
another. Security should be set for this option so it is not
available to most callers. When a file is moved, the file
name, file size, file date and file description from the
original SFFILES.BBS is appended the the SFFILES.BBS of the
File Area to which the file is being moved.
Files may be tagged for shuffling from one file area to
another. Upon selecting this feature, you are prompted
to enter the name(s) of the file(s) you wish to move.
If you have tagged files prior to selecting this feature,
when prompted for the file name, it will default in
automatically. You are then asked to enter the file area
you wish to move the file to. Pressing Enter will list the
file areas or you may may opt to quit. This continues until
until all tagged files are processed and no file name is
entered for moving.
If no files have been tagged and you select the Shuffle Files
option, you will be prompted to enter the file name. Next,
you will be asked to enter the file area to which you wish to
move the file. Pressing enter will list the available file
areas or you may opt to Quit. This process will continue
until no file name is entered for moving.
When Shuffling files, SPITFIRE tests to see if the file to be
moved exists in the target File Area and if it exists, then
the operation is aborted with a message.
<N>.... New Files
This feature allows a caller to search a specific File Area
or all File Areas since a specific date or since the last
time the caller searched for new files. In addition to
listing the new files, a file statistics message is
displayed to the caller with the number of new files
Page 97
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
received since last checked, the total number of files
available for download on the BBS and the number of bytes
of downloadable files which exist on the BBS. SPITFIRE does
not include any CD-ROM File Areas in the search for new
files. SPITFIRE does not report file statistics on a BBS
containing CD-ROM File Area(s) since the statistics are not
accurate due to skipping the CD-ROM File Area(s).
When listing new files, SPITFIRE offers file tagging
for ease of downloading. SPITFIRE precedes each file in
the list with a tag character (with the exception
of S which is used to Stop the file display). As each screen
completes displaying, the caller is prompted to enter
the tag character(s) associated with a file(s) to be
downloaded. When the caller begins the file download
transfer, SPITFIRE automatically inserts the name of the
file(s) the caller has tagged for downloading.
<T>.... Text Search
This feature allows a caller to search for certain text
within a file description. SPITFIRE supports multi-word text
searches and allows up to 6 key words to be searched for at
one time. The caller can search a specific File Area or all
File Areas. Please note that this feature searches ONLY the
file description and not the file name, date or size. These
are displayed, however, when the matching text is located.
<F>.... Find A File
This feature allows a caller to search a specific File Area
or all File Areas for a certain file. Wildcards are allowed,
with the exception of *.*. If a caller enters a file name
without the file extension, SPITFIRE automatically adds a
".*" to the file name. If there is a match, the file name,
size, date and description are shown, provided the file
is listed in the SFFILES.BBS.
<X>.... Xpert Mode Toggle
This feature changes a caller's status from a novice to an
expert or vice versa. If a caller is set as a novice, then
the menu descriptions scroll by after each command. If
a caller is set as an expert, then only the command letters
scroll by after each command.
<?>.... HELP With Commands
This feature displays help for each command available
from the FILE MENU. This feature is augmented with
SFHELP.EXE, which creates separate help screens for each
individual command. For more information on SFHELP.EXE,
consult the documentation accompanying it. This program is
available for download on Buffalo Creek's BBS.
Page 98
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<K>.... File Menu Extension
This command can be used to run third party programs which
are configured by the Sysop. It is set up by including the
necessary commands to execute the desired option within the
SFMESS.BAT file. It should be noted that Sysops need to
use the SFHELP.EXE utility to modify the SPITFIRE.HLP file
so it properly explains the added option.
<@>.... Sysop Utilities
This feature takes a caller from the FILE Section to the
SYSOP Section. The BBS is maintained from the SYSOP Section.
This feature is not normally available to most callers.
<V>.... View A File Archive
This feature allows a caller to view the contents of a ZIP
file. The caller sees the file name, file size and file
date of each file within the compressed ZIP file. The caller
does not have to be in a specific file area to utilize this
feature.
<R>.... Read A Text File
This feature allows a caller to read a text file available
for download. The caller may want to use this feature and
simply capture the text to save downloading the file. The
caller does not have to be in a specific File Area to utilize
this feature.
11.3 UPLOAD/DOWNLOAD PROTOCOLS
-------------------------------
The following is a list of Upload & Download protocols available
by SPITFIRE:
1) Ascii
2) Xmodem Checksum
3) Xmodem CRC
<* D/L only> 4) 1K-Xmodem <Ymodem>
5) SEAlink Derived
6) Telink
* 7) Ymodem Batch
* 8) SEAlink Derived Batch
9) Ymodem-g <Error-correction modems>
* 10) Ymodem-g Batch <Error-correction modems>
SPITFIRE does not allow a caller to download files with a .COM,
.EXE, .ARC, .ARJ, ZIP, or PAK extension when using the ASCII transfer
protocol.
Page 99
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Batch transfers using the External Protocol drivers are supported
by SPITFIRE. (For more information refer to the section - EXTERNAL
FILE TRANSFER PROTOCOLS - of this manual.)
11.4 BATCH DOWNLOAD MENU
------------------------
In order for the Batch Download Menu to be displayed the caller
must have selected to download a file from the File Menu and then
selected a file transfer protocol that is capable of doing batch
downloads. It is possible for a caller to do a batch download without
ever having the Batch Download Menu displayed to them. The Batch
Download Menu is displayed if, after filling their batch queue, the
caller responds "N" when prompted as to whether to begin the batch
transfer now or if when their batch queue is empty and the caller
presses return when asked to enter the name of the file to be
downloaded.
The SPITFIRE default Download Batch Menu looks like this:
>>>> BATCH DOWNLOAD MENU <<<<
<A>...... Add To Batch Queue <V>..View Tagged/Queued List
<B>..... Begin File Transfer <R>... Remove File From List
<S>... Start New Batch Queue <L>.. List Files (This Area)
<C>........ Change File Area <Q>....... Quit To File Menu
<?>.................... Help <G>....... Goodbye & Log Off
BATCH MENU - [A V D R S L C Q ? G]?
<A>... Add To Batch Queue
This feature allows the caller to enter the name of the
files(s) to be added to the batch queue. SPITFIRE does not
allow the caller to exceed their daily download limit or time
limit.
<V>... View Tagged/Queued List
This feature allows the caller to review the file(s) they have
tagged or added to the batch queue. SPITFIRE also informs the
caller of the approximate time required for the file transfer
of each file, as well as the total approximate time to transfer
the entire batch queue.
<B>... Begin File Transfer
This feature simply starts the batch download provided the
caller has files to download listed in the batch queue. Before
the download(s) is started, the caller is prompted as to
whether they wish to log off when the transfer is finished. If
the answer is Yes, SPITFIRE automatically logs the caller
off after the download(s) has completed.
Page 100
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<R>... Remove File From List
If the caller changes his/her mind about including a
file in their list of files to download, this feature allows
removal of that file from the list.
<S>... Start New Batch Queue
In the event the caller decides to start over, this feature
allows the caller to clear all file names currently contained
in the batch queue.
<L>... List Files (This Area)
This feature displays the files in the current File Area
which are available for the caller to download. The file's
name, file size, file date and a brief description of the
file are displayed to the caller.
<C>... Change File Area
This feature allows the caller to change to a different File
Area. If the caller selects <Q>uit, the caller remains in
the present File Area. If the caller presses the [ENTER] key,
SPITFIRE lists the File Areas available to the caller. If
a number corresponding to an available File Area is entered,
SPITFIRE makes that File Area the current File Area.
<Q>... Quit To File Menu
This feature takes the caller from the Batch Section of
SPITFIRE to the File Section of SPITFIRE. If this is selected,
the caller's batch queue is cleared.
<?>... Help
This feature offers a brief description of the various
commands available from the Batch Download Menu.
<G>... Goodbye & Log Off
This feature simply allows the caller to log off the BBS.
11.5 BATCH UPLOAD MENU
----------------------
For the Batch Upload Menu to be displayed, the caller must
select to upload a file from the File Menu and select a file
transfer protocol that is capable of doing batch file transfers.
It is possible for a caller to do a batch upload without ever having
the Batch Upload Menu displayed to them. The Batch Upload Menu is
displayed if, after filling their batch queue, the caller responds
"N" when prompted as to whether to begin the batch transfer now or
if when their batch queue is empty and the caller presses return
when asked to enter the name of the file to be uploaded.
SPITFIRE's default Upload Batch Menu looks like this:
Page 101
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
>>>>> BATCH UPLOAD MENU <<<<<
<A>...... Add To Batch Queue <W>... What's In Batch Queue
<B>..... Begin File Transfer <R>.. Remove File From Queue
<S>... Start New Batch Queue <L>.. List Files (This Area)
<C>........ Change File Area <Q>....... Quit To File Menu
<?>.................... Help <G>....... Goodbye & Log Off
BATCH MENU - [A W U R S L C Q ? G]?
<A>... Add To Batch Queue
This feature allows the caller to enter the name of the
files(s) to be added to the batch queue. SPITFIRE prompts
the caller to enter the file name and a description of the
file to be uploaded.
<W>... What's In Batch Queue
This feature allows the caller to review the file(s) that have
been added to the batch queue. SPITFIRE displays the
file name(s) and a brief description of the files currently
contained in the batch queue.
<B>... Begin File Transfer
This feature simply starts the batch upload provided that the
caller has files to upload listed in the batch queue. Before
the upload(s) are started, the caller is prompted as to
whether they wish to log off when the transfer is finished. If
the answer is <Y>es, SPITFIRE automatically logs the caller
off after the upload(s) are complete. If the caller fails to
provide a description for a file in a batch upload, SPITFIRE
provides a default description: "No Description Provided".
<R>... Remove File From Queue
This feature allows a caller to remove a file from the
batch queue if the caller changes their mind as to
whether a file should be included.
<S>... Start New Batch Queue
In the event the caller decides to start over, this feature
allows the caller to clear all file names currently contained
in the batch queue.
<L>... List Files (This Area)
This feature displays the files in the current File Area
which are available to the caller. The file's name, file size,
file date and a brief description of the file are displayed
to the caller.
Page 102
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<C>... Change File Area
This feature allows the caller to change to a different File
Area. If the caller selects <Q>uit, the caller remains in
the present File Area. If the caller presses the [ENTER] key,
SPITFIRE lists the File Areas available to the caller. If
a number corresponding to an available File Area is entered,
SPITFIRE makes that File Area the current File Area.
<Q>... Quit To File Menu
This feature takes the caller from the Batch Section of
SPITFIRE to the File Section of SPITFIRE. If this is selected,
the caller's batch queue is cleared.
<?>... Help
This feature offers a brief description of the various
commands available from the Batch Upload Menu.
<G>... Goodbye & Log Off
This feature simply allows the caller to log off the BBS.
12.0 SYSOP SECTION EXPLAINED
-----------------------------
Almost all the Sysop utilities are contained in SPITFIRE. No
external programs are needed to do normal, day-to-day maintenance.
However, it is our hope that people will implement utilities for
SPITFIRE. In the event you are interested in writing such a utility
and need detailed information regarding how SPITFIRE interacts with
different support files, please feel free to contact Buffalo
Creek's BBS (515-225-8496).
>>>>>>>> SYSOP MENU <<<<<<<<
<D>.............. Drop To DOS <E>................. Event Menu
<F>............... File Areas <G>.......... Goodbye & Log Off
<H>............ List Comments <I>............ Pack Users File
<J>........ Pack Message Base <R>.... Remove Backup/Log Files
<M>...... Message Conferences <P>........... Print Users File
<Q>........ Quit To MAIN MENU <U>............... Modify Users
<V>........... View Log Files <X>......... Expert Mode Toggle
SYSOP MENU [D E F G H I J R M P Q U V X]?
12.1 SYSOP MENU EXPLANATION
----------------------------
<D>.... Drop to DOS
This feature allows you to drop to DOS from a remote
location. You need to use the ALT+J feature or ALT+D
Page 103
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
feature to drop to DOS locally. When this feature is used
from a remote location, SPITFIRE does not allow the caller
to drop to DOS unless the drop-to-DOS password is properly
entered. This password is configured using the ALT+Z
command at the "Ready..." prompt. It is recommended that
this feature be made available to only trusted callers (if
made available at all.) When this feature is utilized,
SPITFIRE shells to SFREMOTE.BAT and sends a parameter
which indicates the COMM port being used.
<E>.... Event Menu
This option is used for maintaining events used on the
BBS. It is used to List Events, Enable An Event and
to Disable An Event. For more detailed information, refer
to the EVENTS MENU EXPLANATION section of this manual.
<F>.... File Areas
This displays the File Area System Record's Menu. From
this menu, you are able to configure or modify the File
Area System Records. For more detailed information,
refer to the section - CONFIGURING FILE AREA RECORDS of
this manual.
<G>.... Goodbye & Log Off
This feature simply allows the caller to log off the BBS.
<H>.... List Comments
This feature searches Message Conference #1 for messages
addressed to the Sysop. If any messages are found, the
SPITFIRE will prompt you as to whether you wish to preview
messages. Responding with a Y allows the Sysop to read
messages but they are not marked as having been received.
If no messages are found, SPITFIRE notifies you that there
are no messages addressed to you.
<I>.... Pack Users File
This feature allows you to pack SFUSERS.DAT. When selected,
SPITFIRE shells to SFPCKUSR.COM. SFPCKUSR.COM must reside
in the SPITFIRE home directory.
When you select this feature, SPITFIRE asks if you wish to
purge inactive callers. If you answer "Y", you will then
be asked whether to purge callers that haven't called for
<x> amount of days. The value of <x> is determined by you.
After responding to these prompts, SPITFIRE shells to
SFPCKUSR and passes to it the purge criteria you have
supplied.
Page 104
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFPCKUSR will purge from the caller's data base any callers
which have been marked for deletion. If you have opted to
purge inactive callers, any caller who has not called for
the amount of days you specified will also be purged.
Once SFPCKUSR has completed packing the caller's data base,
information regarding the callers purged is written to
SFPURGED.USR (or appended to the existing file) in the WORK
directory and control is returned to SPITFIRE.
SPITFIRE allows you to toggle whether a purge will be
allowed or not allowed for each caller. If a caller has
been toggled to "purge not allowed," SFPCKUSR will not
purge the caller (even if they have not called for the
<x> amount of days specified.)
If you are operating a multi-node system, SPITFIRE does not
allow you to pack the callers file while a caller is on any
of the available nodes. Also, if you are packing the
callers file and a caller attempts to log on, after entering
their name and password, SPITFIRE notifies the caller that
system maintenance is being performed, asks the caller to
call back later and then logs the caller off the BBS. The
Sysop may create their own ASCII/ANSI display screen,
SFMAINT.BBS/CLR, which is displayed here, if found.
It should be noted that if you select this option and are
calling remotely, once you have answered the prompts
supplied by SPITFIRE you will not be able to view the
progress of SFPCKUSR. No remote display is provided
by SFPCKUSR. Display will return when control is returned
to SPITFIRE.
<J>.... Pack Message Base
When this feature is selected, Sysops are asked if they are
sure they want to pack the message base. A "Y" response
causes SPITFIRE to shell to SFPCKMSG.COM which goes through
the message files, purging all messages that have been
marked for deletion. When configuring Message Conference
records the Sysop specifies how old a message must be (in
number of days) for purging with the Purge Messages Older
Than option. From the Message Conference record, the Sysop
also configures whether threaded and unreceived messages are
to be purged when packing the message base. This criteria,
defined for each Message Conference, determines what messages
are purged when packing the message base. It is recommended
that the message base be packed on a regular basis for a
couple of reasons:
<1> Disk space.
<2> Speed (SPITFIRE works faster with fewer messages).
Page 105
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
On multi-node systems, SPITFIRE will not permit packing of
the message base while a caller is on any of the available
nodes. Also, if while packing the message base a caller
attempts to log on, after entering their name and password,
SPITFIRE notifies the caller that system maintenance is
being performed, asks them to call back later. It then
logs the caller off the BBS. The Sysop may create their
own ASCII/ANSI display screens, SFMAINT.BBS/CLR, which are
displayed here if found.
<R>.... Remove Backup/Log Files
When selected, this option displays the following menu:
>>> FILE REMOVAL MENU <<<
<C>.... Erase CALLERS.LOG
<H>... Erase HEYSYSOP.LOG
<S>... Erase SFPURGED.USR
<U>.... Erase SFUSERS.$??
<Q>................. Quit
FILE REMOVAL MENU - [C H U Q]?
<C>... Erase CALLERS.LOG
Selecting this option will cause the existing CALLERS.LOG
file to be erased. SPITFIRE will automatically create a
new CALLERS.LOG file.
<H>... Erase HEYSYSOP.LOG
Selecting this option will cause the existing HEYSYSOP.LOG
file to be erased. SPITFIRE will automatically create a
new HEYSYSOP.LOG file.
<S>... Erase SFPURGED.USR
When this option is selected, SFPURGED.USR will be erased.
SPITFIRE will automatically create a new SFPURGED.USR file
the next time the SFUSERS.DAT file is packed.
<U>... Erase SFUSERS.$??
When this option is selected, the SPITFIRE caller's backup
files are erased.
<M>.... Message Conferences
This displays the Message Conference System Record's Menu.
From this menu, Sysops can configure or modify the
Message Conference System Records. For more detailed
information, refer to the section - CONFIGURING MESSAGE
CONFERENCE RECORDS.
<P>.... Print Users File
If the printer is turned on and ready for use and this
feature is selected, the Sysop is prompted to select
Page 106
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
one of the following options: Print to <D>isk, <P>rinter,
<Q>uit?. If the printer is not turned on and ready,
only the options: Print to <D>isk, Quit will be displayed
Print to <D>isk creates a text file in the WORK file
directory named SFUSERS.LST. This file contains such
information as caller name, city/province, and phone
number for each caller in the database. <P>rint will
send the information to the printer for each caller
in the database. <Q>uit returns you to the Sysop Menu.
<Q>.... Quit to MAIN MENU
This feature takes you from the Sysop Utility Section of
SPITFIRE to the MAIN MENU.
<U>.... Modify Users
This feature is the same as selecting ALT+A at the
"Ready..." prompt. The menu that accompanies this
selection is self-explanatory. This feature is used to
change statistics on any caller and to manually add new
callers. For further information, refer to the section -
SPECIAL FUNCTION KEY DEFINITIONS of this manual.
<V>.... View Log Files
Selecting this option causes the following sub-menu to
be displayed:
>> View Log File Menu <<
<C>..........CALLERS.LOG
<H>.........HEYSYSOP.LOG
<N>...........SFNEWU.REP
<O>.......SFORDER<x>.REP
<S>.........SFPURGED.USR
<Q>.................QUIT
Depending on your selection, you are able to review the
Caller's log, Heysysop log, replies to the new user
questionnaire, responses to the Main Menu questionnaire
files, or the purged caller listing. If <O> is selected
for viewing the questionnaire/order file replies, you are
prompted to enter the letter corresponding to the
SFORDER<x>.REP file you wish to have displayed.
Upon selecting the desired log, Sysops are then presented
with the following options for reading the log file:
<T>..Today's Date
begins displaying the CALLERS.LOG, HEYSYSOP.LOG,
SFPURGED.USR or SFNEWU.ANS from its first entry for
the current day.
Page 107
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
<B>..Beginning Of File
displays the CALLERS.LOG, HEYSYSOP.LOG, SFNEWU.ANS
or SFPURGED.USR from the beginning of the file,
starting with the first entry.
<S>..Specify Date
prompts for a date to be entered and will begin
displaying the CALLERS.LOG, HEYSYSOP.LOG, SFPURGED.USR
or SFNEWU.ANS with the first entry for the date that
is entered. If the date specified here can not be
found, SPITFIRE searches for the next newer date
than what was specified and displays the file from
that point forward.
<Q>..Quit
Returns you to the Sysop Menu.
<X>.... Xpert Mode Toggle
This feature changes caller status from a novice to an
expert or vice versa. If set as a novice, the menu
descriptions scroll by after each command. If set as an
expert, only the command letters scroll by after each
command.
13.0 SPECIAL COMMANDS FOR SYSOP STATUS
---------------------------------------
Definition of Sysop Status
--------------------------
A caller with Sysop Status is defined as any caller that has a
security level equal to or greater than the Sysop security level as
set using the ALT+Z feature at the "Ready..." prompt.
The Message section has a few "Special Commands" for callers with
Sysop Status.
When a system is configured to allow a caller the ability to
delete messages, it's important to note that only the sender and
receiver can delete messages, except for callers with Sysop Status.
Any caller with Sysop status can read, delete, and un-delete any
message.
Any caller with Sysop Status may enter messages into message
conferences even though it is configured to be a Read only Message
Conference.
Page 108
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
If a message conference is configured not to allow Caller Message
Deletion and the caller enters a net-mail message, the prompt 'Purge
message after it is sent? [y/N] will not appear unless the caller has
Sysop status.
The <P>rivate command is a toggle that can be used to make a
non-public message public and a public message non-public.
The <C>opy command will allow a caller with Sysop security to
move a message to another Message Conference and forward the message
to another caller other than the original recipient of the message.
Last in the message arena is the <U>ndelete command. Anyone with
Sysop Status will automatically be able to read all the messages in
the message system, even if they have been deleted. Those who see a
message which has been marked for deletion may undelete it by using
this command. Callers are not able to read deleted messages unless
their access level is equal to or greater than Sysop Status.
When a message is Undeleted, changed from Non-public to Public or
changed from Public to Non-public, the message is re-displayed so
the change can be verified. When a message is changed from Non-public
to Public, an option is given allows the message to be addressed to
"All Callers".
If a caller with Sysop Status attempts to upload a file that
already exists, that caller is given the opportunity to overwrite
the file. The caller is warned that the file already exists and is
given the option to overwrite it. SPITFIRE does not allow any other
caller without Sysop Status this privilege.
13.1 SPECIAL COMMANDS FOR SYSOP
--------------------------------
The Sysop is determined within the ALT+Z configuration window.
The name entered as Sysop Caller Name is used by SPITFIRE to
determine the name of the Sysop. Messages left using the <C>omment
to Sysop feature from the Main Menu feature are displayed to the
person logging on under this name.
The Sysop has one feature available to them that no other callers
have, regardless of the caller's security. When selecting the option
to read messages, if recognized as the Sysop, callers are prompted as
to whether they wish to preview messages. This means that they will
be able to read messages but the messages will not be marked as having
been received. A handy use for this feature may be when Sysops don't
have time to respond to all their messages. They can still read the
messages and respond to those they choose. Callers will not see that
Page 109
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Sysops have received the message and feel slighted by the fact that
there was no response. Sysops can re-read messages later and respond
when they have more time to devote to responding to messages. Also,
those with Sysop-Level security have an "unlimited" number of daily
node chats of "unlimited" duration.
14.0 EVENTS MENU EXAMPLE
------------------------
It is possible for a Sysop to automatically execute specific
programs automatically by setting these programs up as a scheduled
event using SPITFIRE's Events Menu.
>>>>>>>> EVENTS MENU <<<<<<<<
<L>............ List An Event <E>.......... Enable An Event
<D>......... Disable An Event <Q>..................... Quit
<+>............... Next Event <->........... Previous Event
EVENTS MENU - [L E D Q + -]?
14.1 EVENTS MENU EXPLANATION
-----------------------------
<L>.... List An Event
SPITFIRE supports 13 events <A..M>. Sysops who select
this feature are asked which event <A..M> they wish to
view. If the event selected is not configured,
SPITFIRE states that this event is not active. If the
event selected is configured, then SPITFIRE displays
the time of the event, the day of the event, whether
the event is active and whether it has been completed
that day.
<E>.... Enable An Event
This feature is used to activate one of the 13 scheduled
events available. Sysops who select this feature are
asked which event they wish to enable. If they select
one that is already active, SPITFIRE notifies them that
the event selected is already active and they are asked
whether they wish to change it. If the designated
event is not active, Sysops are prompted to enter the
time the event is to be activated (expressed in military
time. Example: 22:00 = 10pm). Next they are asked on
what day the event should be scheduled for.
The format looks like this:
0=Sunday, 1=Monday, 2=Tuesday, etc....7=All!
Page 110
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Sysops are then prompted as to whether the event should
be marked as having been completed for the day. If they
reply with N for No, and the event is configured to be
executed at a time earlier than when it is created, the
event is executed upon exiting the Events Menu. If they
reply with N for No, and the event is configured to be
executed at a time later than when it is created, it is
executed at the next scheduled time. If they reply with
Y, for Yes, the event is not executed until the next
designated scheduled time after the day it is created.
Finally, Sysops are prompted as to whether the event
should be marked as an on-time event. If an event is
marked as an on-time event, when a caller logs onto the
BBS, SPITFIRE checks their time against any on-time event
that has not been completed for that day. If the event is
scheduled to run during the amount of time the caller has,
SPITFIRE reduces their amount of time on the BBS by that
amount. For example, if a caller is allowed 60 minutes when
logging onto the BBS, and SPITFIRE checks for an on-time
event and determines an on-time event is to be executed in
25 minutes, the time the caller is allowed on the BBS for
the current call is reduced to 25 minutes.
**NOTE** Even though an event is marked as an on-time event, it
is possible that a caller could gain additional time on the
BBS preventing the event from being executed on-time. For
example, the BBS could be configured to allow additional
time for file uploads (i.e. 2 to 1 time compensation for
uploads) or offer time bank programs where the caller can
withdraw stored online time.
After having selected the desired scheduled event and
establishing the time and day the event is to be
performed, Sysops need to modify the SF.BAT file with
their favorite text editor. For illustration purposes,
let's assume Sysops wish to execute Buffalo Creek
Software's SFLOG to create a bulletin of the weekly
activity on their BBS. SFLOG requires Sysops to
specify the bulletin file name that the information will
be written to by adding a "/BULLET<x>" to the command
line parameter. Our example will use the file BULLET1.
To simplify this explanation, assume all files are being
run from the default directories, and the event will be
event A.
The Sysop will need to select <E>.... Enable An Event
from the Sysop Utilities Menu and then choose A as the
event to be created. They are then prompted for the time
Page 111
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
the event will be performed. Let's assume a time of 01:00.
Next, the Sysop is prompted for the day the event will
be performed. Let's assume they wish to run the event
every Sunday, so 0 is entered. When prompted whether to
mark the event as being completed they type Y. Finally,
Sysops are prompted as to whether the event should be an
on-time event and N is entered.
The SF.BAT file for Event A will look like this:
:EVENT_A
REM Place Event Commands Here
GOTO LOOP
What is required next is to include all necessary DOS
commands which are needed to run the SFLOG program
and enter those in place of the "REM Place Event Commands
Here".
A completed SF.BAT for Event A appears as:
:EVENT_A
CD\SF\WORK
SFLOG /BULLET1
COPY BULLET1.* \SF\DISPLAY
ERASE BULLET1.*
CD\SF
GOTO LOOP
With the event set up up as described, every Sunday morning
at 1:00 am (or immediately after a caller logs off since it
has not been marked as an on-time event), SFLOG creates a
list of the BBS weekly activity. SFLOG must be located in
the same directory as the CALLERS.LOG (WORK). Therefore,
the batch begins by changing to that directory. SFLOG is
then executed and the BULLET1.BBS/CLR display files are
created. Next, the bulletins are copied to the DISPLAY file
directory and to conserve disk space the BULLET1.BBS/CLR
files in the WORK directory are deleted.
<D>.... Disable An Event
This feature is used to disable an event that has been
configured previously. If the event is currently active,
SPITFIRE asks the Sysop whether they are certain they want
to disable it. Responding with "Yes" disables the scheduled
event.
<Q>.... Quit
This feature takes the caller from the Events Menu and
Page 112
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
returns them to where SPITFIRE was prior to calling up
the Events Menu, either the "SPITFIRE ready..." prompt
or the Sysop Utilities Menu.
<+>.... Next Event
This option is used to move forward from one Event to
another. Pressing the "+" key progresses from one
event to the next in alphabetical order. When the last
event is reached (Event M) and the "+" key is pressed
SPITFIRE cycles to the first event, Event A.
<->.... Previous Area
This option enables Sysops to cycle through the Events in
reverse order. Pressing the "-" key moves to the
preceding event. From Event A, if the "-" key is pressed
SPITFIRE will cycle to Event M, the last event.
IMPORTANT NOTE REGARDING SCHEDULED EVENTS!
------------------------------------------
SPITFIRE has the capability of marking an event as an "on-time"
event, which causes the event to be executed at the exact time for
which it has been set up. If an event is marked as an on-time event,
when a caller logs onto the BBS, SPITFIRE checks their time against
any on-time event that has not yet been completed for that day. If the
event is scheduled to run during the amount of time the caller has,
then SPITFIRE reduces their amount of time on the BBS by that amount.
For example, if a caller is allowed 60 minutes when logging onto the
BBS, and SPITFIRE checks for an on-time event and determines an on-time
event is to be executed in 25 minutes, the time the caller is allowed
on the BBS for the current call is reduced to 25 minutes.
**NOTE** Even though an event is marked as an on-time event, it
is possible that a caller could gain additional time on the BBS
preventing the event from being executed on-time. For example, the
BBS could be configured to allow additional time for file uploads
(i.e. 2 to 1 time compensation for uploads) or offer time bank
programs where the caller can withdraw stored online time.
Marking an event as on-time event might be necessary for running
programs that require a specific time to be executed. Such an
instance might be importing daily net-mail where Sysops are given
a designated amount of time for connecting with their hub. Usually
configuring an event to activate "on-time" is not necessary.
When an event is not marked as an on-time event, unlike most
other Bulletin Board Systems, if a caller is on-line when an event is
scheduled to occur, SPITFIRE waits until the caller logs off and then
Page 113
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
performs the scheduled event. In this fashion, the caller is not
interrupted or subject to a forced log-off.
Please note the Event M is reserved for use to Pack the Message
Base. At the scheduled time you designate, SPITFIRE initiates Event M
to pack the message base by purging all messages marked for deletion.
In addition to messages marked for deletion, messages are purged based
on how the Sysop has configured the Message Conference Record. The
options which determine which messages will be purged include Purge
Msgs Older Than, Purge Unreceived Msg, and Purge Old Thread Msg. Purge
criteria is configured individually for each Message Conference that is
available on the BBS. Refer to the section - Setting Up System Records
for more information regarding these options.
Immediately after completing the scheduled event M, SPITFIRE
looks for SFMSGPCK.BAT in the work file directory. If it exists,
SPITFIRE shells to and executes the commands within the
SFMSGPCK.BAT. This batch is intended to perform duties required by
some net-mail utility drivers. If SFMSGPCK.BAT is not found or once
it has been completed, SPITFIRE returns to the "Ready..." prompt.
Packing the message base should be done routinely to conserve disk
space.
15.0 HARDWARE/SOFTWARE DATA FLOW CONTROL
----------------------------------------
When Sysops select ALT+M to configure your modem, they will
notice a Hardware Data Flow Control switch. This switch is turned on
(Yes) when Sysops use a modem that automatically adjusts to the
baud rate of the incoming call rather than depending upon the software
to reset the baud rate of the COMM port. If the switch is set to
Yes, then SPITFIRE does not adjust the COMM port to the baud rate of
the incoming call. If the switch is set to No, then SPITFIRE adjusts
the COMM port to the baud rate of the incoming call. One case of
having this switch set to YES is when using a USR HST modem at 19200
baud. In this case Sysops need to use the modem initialization string
mentioned earlier in this manual. Those who are not sure if their
modem adjusts to the baud rate of the incoming call should refer to
their modem manual.
16.0 SCREEN SAVE FEATURE
-------------------------
SPITFIRE contains its own Screen Save Feature to prevent
screen-burn. Sysops who are presently using a memory-resident
screen-save utility should discontinue its usage in favor of
this feature.
Page 114
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
17.0 SPITFIRE DOORS SECTION
---------------------------
This feature is designed to allow the use of third party
programs (normally referred to as door programs) which are not a part
of SPITFIRE. SFGUESS is a sample door program written to demonstrate
how to configure a door program for use with SPITFIRE. SFGUESS is
included in the SPITFIRE Bulletin Board System distribution package
and can be played on a BBS after it has been installed on a SPITFIRE
BBS.
What follows is a step-by-step set up procedure for SFGUESS. This
is provided to demonstate the process and assist Sysops in future door
installations.
A brief explanation of the SPITFIRE Door Menu structure is
beneficial to understanding the installation of a SPITFIRE door.
SPITFIRE supports up to 24 doors. Alphabetical characters are
used to initiate the door commands, A through Z, with two exceptions.
The G (Goodbye) is used to log the caller off the BBS and Q (Quit)
returns the caller to the Main Menu. Therefore, the SFDOOR.MNU file
can have a maximum of 24 lines, one for each door program available
on the system.
For this example, it is assumed that there are not any doors
presently set up. It is also assumed that SPITFIRE is being run on
drive C in a directory named SF. In the event Sysops are running
SPITFIRE on a different drive and/or in a different directory than
C:\SF, then the SF.BAT file example (listed below) will have to be
altered to reflect the correct drive and directories.
What follows is a step-by-step description of the procedure
utilized to configure a SPITFIRE Door. The first thing to do is
create the file named SFDOOR.MNU, using a favorite text editor.
When created, SFDOOR.MNU is placed in the system files directory.
When configuring only door A, SFDOOR.MNU will have only 1 line.
For demonstration purposes, this line can look like any of these:
Guess A Number,SEC>=10
Guess A Number,SEC=10
Guess A Number,SEC<10
The name of the door (as it appears in the Door Menu) comes
first in the line and is limited to 25 characters. This is followed by
a comma, which is used to tell SPITFIRE where to end the name of
the door and where to start reading the security level of the door.
The Sysop controls access to the door through the security function.
Using SEC>=[x], where [x] is the numeric value of the security level,
any caller with a security equal to or greater than [x] can access
Page 115
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
the door. If SEC=[x] is used on a caller with the security level of
[x] can access the door and if SEC<[x] is used only a caller with the
security level less than [x] can access the door. Using SPITFIRE's
default menus, this door does not display to any caller with a security
level less than 10.
Buffalo Creek Software provides a menu driven utility that easily
creates and/or modifies the SFDOOR.MNU file. SFDOOR.ZIP is included
in the SPITFIRE package and can be downloaded from Buffalo Creek's BBS.
The next step in setting up the door is to create a sub-directory
of the SF directory named DOOR_A and move the SFGUESS.EXE file into
the DOOR_A directory. The DOS manual can be referred to for information
on how to create directories.
Edit the SF.BAT file with your favorite text editor. At the
point where the SF.BAT file reads :DOOR_A place the door A commands
(must be valid DOS commands) between :DOOR_A and GOTO LOOP. That
portion of the SF.BAT file should be changed to read as listed below:
:DOOR_A
COPY SFDOORS.DAT C:\SF\DOOR_A
CD\SF\DOOR_A
SFGUESS
ERASE SFDOORS.DAT
CD\SF
GOTO LOOP
:DOOR_B
After saving the changes in the SF.BAT file to disk, boot
SPITFIRE using the SF.BAT file. At the "SPITFIRE ready for..."
prompt, log on locally either using the ALT+S or ALT+Q
keystrokes. At the Main Menu, select "<S>... SPITFIRE Doors".
The Door Menu should appear something like this:
>>>>>>>>> DOOR MENU <<<<<<<<<
<A>... Guess A Number <?>... Door Bulletins
<Q>... Quit <G>... Goodbye
DOOR MENU - <A ? Q G>?
If <A> is selected at this point, SPITFIRE displays a message
that states "Executing Door A... Please stand by!". At this point,
SPITFIRE writes a text file named SFDOORS.DAT and a file named DOOR.SYS
to the drive. (SFDOORS.DAT contains necessary caller information for
executing doors on a SPITFIRE BBS and DOOR.SYS is the universally
accepted format containing caller information by those attempting to
standardize the door caller information file. These files are created
when a caller enters a door and SFDOORS.DAT is automatically erased
Page 116
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
when the caller returns to SPITFIRE.) SPITFIRE, after creating the
SFDOORS.DAT and DOOR.SYS files, terminates, sending the appropriate
DOS ERRORLEVEL to the SF.BAT file. In the case of door A, SPITFIRE
sends an ERRORLEVEL of 34 to SF.BAT which causes the commands placed
between :DOOR_A and GOTO LOOP to be executed. In the event the
correct commands were entered between :DOOR_A and GOTO LOOP, SFGUESS
will run. When the door is finished running, SPITFIRE re-boots
and the caller is returned. If the Sysop has the BBS configured to
require a password when returning from a door, the caller is prompted
for their password.
If a caller enters a door while logged on SPITFIRE, there are
up to three tests SPITFIRE performs when a caller returns to SPITFIRE,
after exiting the door program. First, SPITFIRE must find SFDOORS.DAT
in the system files directory. Second, SPITFIRE must find a carrier
detect. And third, if the Sysop has configured the BBS to require a
password when returning from a door, the caller must enter the correct
password when prompted for it. In the event a door is entered during a
local log on, SPITFIRE will perform the following test(s): SPITFIRE
must find the SFDOORS.DAT file and, if the Sysop has configured the BBS
to require a password when returning from a door, the correct password
must be entered.
There are numerous door programs, usually Shareware products,
available for download from Buffalo Creek's BBS as well as most
other bulletin boards. Sysops who do not wish to run third party
programs with SPITFIRE through the Door feature, should set the
security level of the SPITFIRE Door command in the SFMAIN.MNU,
SFFILE.MNU and SFMSG.MNU files high enough so that callers cannot
access it.
SPITFIRE Doors can be accessed by a caller from the Main Menu,
provided the caller's security level is high enough. As previously
mentioned, SPITFIRE supports the use of 24 different doors. However,
there are third party programs available that will expand this to
hundreds of doors. An example of such a program is WILDFIRE, which
is a Shareware program by Steve Cox. The newest release of WILDFIRE
can be downloaded from Buffalo Creek's BBS and Flite-Line BBS at
(402) 421-2434.
17.1 SPITFIRE DOORS DISPLAY FILES
---------------------------------
SPITFIRE uses certain display files during the use of the
Doors feature, if such files are found. It is important to note
that SPITFIRE works perfectly without these display files. Listed
below are the display files that can be used in conjunction with
the SPITFIRE door feature:
Page 117
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFDORBUL .BBS/CLR - Non-ANSI and ANSI list of door bulletins
which are available to the caller. This is
displayed to the caller just prior to the
door menu (if available) or when selecting
the <?> command from the door menu. (DISPLAY)
DORBUL<x>.BBS/CLR - Non-ANSI and ANSI <x> file that is displayed
when the corresponding <x> is selected from
the SPITFIRE door bulletin list. This file
can be used to display top score bulletins
created by many of the available door game
programs. (DISPLAY)
SFDR<x> .BBS/CLR - Non-ANSI and ANSI door display menu file
displayed to the caller with a corresponding
<x> security level. (DISPLAY)
SFDOOR<x>.BBS/CLR - Non-ANSI and ANSI screen that is displayed
to the caller after selecting the corresponding
<x> door option and prior to the <x> door
being executed. This file might be used to
send the caller a special message about the
door. (DISPLAY)
SFDORBAK .BBS/CLR - Non-ANSI and ANSI screen displayed to the
caller after quitting the door program and
prior to returning to SPITFIRE. This is
normally used simply to welcome the caller
back to SPITFIRE. (DISPLAY)
17.2 SPITFIRE DOORS SUPPORT
----------------------------
Configuring the use of doors with SPITFIRE is supported by
Buffalo Creek Software for registered callers of SPITFIRE. Please keep
in mind once a caller executes a door, SPITFIRE is totally terminated
from memory and control is passed to the SF.BAT where the commands
configured by the Sysop are executed. Sysops who have problems
with the door program itself should read the documentation and then
contact the author of the program. Please keep in mind that once a
caller has entered a door, SPITFIRE is completely out of memory and has
NO responsibility for the operation of the door program.
Page 118
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
18.0 EXTERNAL FILE TRANSFER PROTOCOLS
-------------------------------------
This feature is designed to allow the use of file transfer
protocols which are not part of SPITFIRE but are rather provided
by sources other than Buffalo Creek Software. An example is ZModem,
a popular protocol written by Chuck Forsberg. There are no External
Protocols distributed with SPITFIRE because they are usually
Shareware products. Buffalo Creek Software most likely has no right
to distribute them with the SPITFIRE program. However, there are
many available for download from Buffalo Creek's BBS, as well as most
other bulletin boards.
It should be noted that SPITFIRE does not allow callers to select
an external protocol as their default file transfer protocol. This is
important for callers to know, so SPITFIRE has provided a means to
notify the caller that External Protocols exist.
When a new caller logs on for the first time and the Sysop has
configured the BBS to require the New Caller Default Protocol option to
display or when callers use the "<Y>... Your Statistics" from the Main
Menu to change their default file transfer protocol, SPITFIRE displays
SFPROMSG.BBS/CLR just before a default file transfer protocol selection
is made. The SFPROMSG.BBS/CLR message can state that if a default file
transfer protocol is chosen, the external protocol option will not be
available. Callers wishing to utilize external protocols should set
their default to <S>.. Select At Time Of Transfer.
18.1 EXTERNAL DOWNLOAD PROTOCOLS
--------------------------------
SPITFIRE allows up to 14 external protocols <A..N> to be utilized
for downloads. It may be best at this point to go through setting up
an external download protocol, step by step.
To start, an assumption is being made that Sysops have a copy of
DSZ (Forsberg's ZModem). Those without a copy may download it from
Buffalo Creek's BBS. Sysops will need to use their favorite text
editor to create a display file named SFEXTDN.BBS. This is a simple
text file which will contain the names of the external protocols
that are available.
For the purpose of setting up ZModem as the first external
download protocol, the SFEXTDN.BBS file has only one line and
looks something like this:
<A> ZModem
Page 119
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Sysops need to place SFEXTDN.BBS in the directory configured as
the Display Files Path. To verify, or modify, the EXTERNAL TRANSFER
FILE PATH, press ALT+P at the SPITFIRE "Ready..." prompt. Selecting
option D allows modification of SPITFIRE's default setting. An
assumption (for demonstration purposes) is being made here that
SPITFIRE is run on the C drive in a directory named SF and that the
External Transfer path is C:\SF\EXTNOD1.
The next step is to place DSZ in the directory set up as
the External Transfer Path (example... C:\SF\EXTNOD1). Next, using
a favorite text editor, a batch file is created named SFEXTDNA.BAT
in the directory designated as the External Transfer Path. SPITFIRE
shells to this batch when a caller selects <A>... from the download
protocol list. It is appropriate at this point to show the suggested
contents of this batch file.
ECHO OFF
BRK OFF
Echo Executing SPITFIRE'S External Protocol #1
CD\SF\EXTNOD1
DSZ %2 sz %3
CD\SF
BRK ON
Now that SFEXTDNA.BAT, with the above listed commands, resides
in the directory set up as the External Transfer Path, the first
External Download Protocol has been configured. The actual contents
of the batch files in use depends upon the specific protocols.
The above is only a sample batch file that should work well with
DSZ.
Before the commands in the above described batch file are
explained, it is important to note when a caller selects <B>...
from the download protocol list, SPITFIRE shells to a batch file
named SFEXTDNB.BAT. As stated before, there are fourteen external
protocols allowed and are denoted by command letters "A" thru "N".
These command letters are used to shell from SPITFIRE to the
corresponding batch files.
A = SFEXTDNA.BAT B = SFEXTDNB.BAT C = SFEXTDNC.BAT
D = SFEXTDND.BAT E = SFEXTDNE.BAT F = SFEXTDNF.BAT
G = SFEXTDNG.BAT H = SFEXTDNH.BAT I = SFEXTDNI.BAT
J = SFEXTDNJ.BAT K = SFEXTDNK.BAT L = SFEXTDNL.BAT
M = SFEXTDNM.BAT N = SFEXTDNN.BAT
An explanation of these batch files and what SPITFIRE does in
preparation to use these batch files is appropriate and important
for Sysops to understand.
Page 120
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the download. If allowable, then SPITFIRE copies the selected file
to the directory configured as the External Transfer Path. PLEASE NOTE
THAT SPITFIRE COPIES THE SELECTED FILE. THIS MEANS THERE MUST BE
ENOUGH DISK SPACE AVAILABLE FOR THE FILE TO BE COPIED. If all tests
were passed and the file was successfully copied, SPITFIRE switches to
the directory configured as the External Transfer Path and stays in
memory but shells to the appropriate batch file (as described above).
Keep in mind that SPITFIRE is resident in memory, as well as a second
copy of the command processor (COMMAND.COM) so the external file
transfer protocol requires some memory. Therefore, the minimum memory
requirement of 256K, stated earlier in the manual, may be insufficient
for systems including the external protocol file transfer options.
Upon performing this shell, SPITFIRE passes at least three
parameters to the appropriate batch file. The first parameter is the
baud rate. The second parameter being passed is the number of the
COMM port being used. The third parameter is the name of the file to
be downloaded. This passed information is needed by most external file
transfer programs and can now be used with DOS batch commands. The
file name is passed in ASCII text as %3. The baud rate is %1, a number
representing baud rate of the caller, such as 2400. The COMM port %2
is the number of the COMM port being used (1,2,3 or 4). Those who are
not familiar with the use of the % command in batch files, should refer
to the DOS manual for specific details.
When the external protocol file transfer program has finished
its work, control is automatically returned to SPITFIRE. Once control
is returned, SPITFIRE switches back to the directory in which the
SPITFIRE system files reside. Next, SPITFIRE erases the file that was
copied to the directory configured as the External Transfer Path for
download. Finally, SPITFIRE checks the amount of time that has passed
during the shell to the external protocol batch file. In the event
SPITFIRE discovers that the time spent in the shell was at least
30% of the estimated transfer time, the number of downloads,
K downloaded, etc. of the caller is updated. In the event the time
spent in the shell was less than 30% of the estimated transfer time,
SPITFIRE assumes that the transfer was not successful and the
caller's data is not updated.
Sysops will notice the example batch file (above) has a command
to change to the directory configured as the External Transfer Path.
They will also notice there is a another command to change back to the
SPITFIRE system files directory. These commands do not have to be in
the batch files created because SPITFIRE will automatically perform
these chores. However, it is quite permissible for the commands to be
in the batch file where they can act as a safeguard. Sysops will
finally notice a command BRK OFF at the beginning of the batch file
Page 121
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
example, as well as a BRK ON at the end. BRK is a Shareware utility
distributed by Solid Systems of Newport News, Virginia. It is used to
disable and enable the CTRL+BREAK, which can be used to terminate a
batch file. Sysops may need this utility for the protection of their
systems. BRK.ZIP can be downloaded from Buffalo Creek's BBS.
18.2 EXTERNAL BATCH DOWNLOAD PROTOCOLS
--------------------------------------
SPITFIRE also allows for batch downloads to be transferred
with the use of external protocols, provided the external protocol
is written to include batch transfers. Much of the information
discussed in the section - EXTERNAL DOWNLOAD PROTOCOLS - also applies
to the External Batch Download Protocols. However, there are some
significant differences which warrant mentioning.
The SFEXTDN.BBS file is created using a favorite text
editor. It lists the names of the external batch file protocols
that are available. On the same line, the protocol description
is followed by a comma and the word BATCH. Continuing to use DSZ
as an example, the SFEXTDN.BBS file might now look like this:
<A> ZModem
<B> ZModem Batch,Batch
The SFEXTDN.BBS must reside in the path assigned as the Display
File Path. The DSZ must be placed in the directory configured as
the External File path. Using a favorite text editor, create a
SFEXTDN<A..N>.BAT file which contains the commands necessary to
execute the batch download. In the above example, SFEXTDNB.BAT
needs to be created to perform external ZModem batch downloads from
SPITFIRE.
The commands for the SFEXTDNB.BAT file should look like this:
BRK OFF
ECHO OFF
ECHO EXECUTING EXTERNAL PROTOCOL # 2
CD\SF\EXTNOD1
DSZ %2 sz %3 %4 %5 %6 %7 %8 %9
CD\SF
BRK ON
The commands used for ZModem batch pass the same command line
parameters (explained above in the EXTERNAL DOWNLOAD PROTOCOLS section)
as the single file ZModem transfer with the addition of %4, %5, %6, %7,
%8, %9. The %3 through %9 are the file names the caller enters if the
batch download external protocol is selected. SPITFIRE allows up to
seven files to be transferred during an external batch download. %3
through %9 represent the file names the caller includes in the batch
queue.
Page 122
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the download. If allowed, SPITFIRE copies the selected files to
the directory configured as your External Transfer Path. PLEASE NOTE
THAT SPITFIRE COPIES THE SELECTED FILES. WITH EXTERNAL BATCH DOWNLOADS
IT IS DOUBLY IMPORTANT TO THAT ENOUGH DISK SPACE BE AVAILABLE FOR THE
FILES TO BE COPIED. However, in adding files to the batch queue if
SPITFIRE discovers the addition of another file exceeds the amount
of available disk space or exceeds the number of daily allotted
downloads for the caller, an appropriate message is displayed prior
to downloading the files presently in the batch queue.
18.3 TEXT FILE EXTERNAL BATCH DOWNLOAD PROTOCOLS
------------------------------------------------
SPITFIRE can be configured to create a text file in the EXTERNAL
directory which contains a list of the files to be downloaded. By
using the file list, the path and name of each file is stored in a text
file. By using the text file, it is no longer necessary for SPITFIRE
to copy the files into the EXTERNAL directory. It should be mentioned
that the external protocol must have the capability of reading this
text file. DSZ is one such external protocol.
There are several advantages to using this particular method with
batch transfer protocol downloads. First, because files are no longer
required to be copied to the EXTERNAL directory, downloads can be
performed much faster. Speed is important for multi-node systems.
Secondly, you eliminate the risk of running out of disk space since
files are duplicated when copied to the EXTERNAL directory for
downloading. Also, the number of files that can be downloaded in a
single batch transfer is significantly increased using the text file.
Where the typical batch download (discussed in the previous section of
the manual) allows 7 files to be downloaded per batch; using the
text file allows 99 files to be downloaded per batch.
To initiate an external batch download protocol using a textfile,
simply add
,UseFile
at the end of the line of your SFEXTDN.BBS where the text file feature
is to be used. For example, here is a sample SFEXTDN.BBS:
<A> ZModem,UseFile
<B> ZModem Batch,Batch,UseFile
The SFEXTDN.BBS must reside in the path assigned as the Display
File Path.
Page 123
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Place DSZ.COM in the directory configured as the External File
path. Using your favorite text editor, Sysops should create a
SFEXTDN<A..N>.BAT file which contains the commands necessary to
execute the batch download. In the above example, SFEXTDNB.BAT is
created to perform an external ZModem batch download from SPITFIRE.
The commands for the SFEXTDNB.BAT file should look like this:
BRK OFF
ECHO OFF
ECHO EXECUTING EXTERNAL PROTOCOL # 2
CD\SF\EXTNOD1
DSZ %2 sz @C:\SF\EXTNOD1\SFEXTRAN.LST
IF ERRORLEVEL 1 GOTO END
IF ERRORLEVEL 0 GOTO GOOD
:GOOD
APPENDIT ZMODEM.TXT \SF\CALLERS.TMP
:END
CD\SF
BRK ON
Note that the commands used in the SFEXTDNB.BAT (above example) uses
the text file C:\SF\EXTNOD1\SFEXTRAN.LST. This is the text file where
SPITFIRE stores the names of the files which the caller has selected
for download.
It should again be noted that when an External Protocol is selected,
SPITFIRE does all the normal tests to be sure it is permissible for the
caller to perform the download. In adding files to the batch queue if
SPITFIRE discovers the addition of another file exceeds the number of
daily allotted downloads for the caller, an appropriate message is
displayed prior to downloading the files presently in the batch
queue.
18.4 EXTERNAL UPLOAD PROTOCOLS
------------------------------
SPITFIRE allows up to 14 external protocols <A..N> to be utilized
for uploads. Since SPITFIRE handles external protocols for uploading
slightly different than downloading, it is a good idea at this point to
go through setting up an upload external protocol, step by step. To
begin, Sysops need to obtain a copy of DSZ (Forsberg's ZMODEM). Those
without a copy can download it from Buffalo Creek's BBS. Using your
favorite text editor, create a display file named SFEXTUP.BBS. This is
a simple text file which contains the names of the external protocols
that are available. For the purpose of setting up ZModem as the first
upload external protocol, the SFEXTUP.BBS file has one line that looks
something like this:
<A> ZModem
Page 124
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SFEXTUP.BBS is placed in the directory configured as the Display
Files Path. To verify, or modify, the EXTERNAL TRANSFER FILE PATH,
press ALT+P at the SPITFIRE "Ready..." prompt. Selecting option D
allows modification of SPITFIRE's default setting. An assumption (for
demonstration purposes) is made that SPITFIRE is run on the C drive in
a directory named SF and that the External Transfer path is
C:\SF\EXTNOD1.
The next step is to place DSZ in the directory set up as
the External Transfer Path (example... C:\SF\EXTNOD1). Next, using
a favorite text editor, a batch file is created named SFEXTUPA.BAT
in the directory designated as the External Transfer Path. SPITFIRE
shells to this batch file when a caller selects <A>... from the upload
protocol list. At this point, prior to executing the commands within
the batch file, SPITFIRE sets the attribute of all files contained in
the External Transfer Path (in this example, C:\SF\EXTNOD1) to Read
Only. This is done to prevent callers from uploading and overwriting
files which exist in your External Transfer Path. It is appropriate
at this point to show the suggested contents of this batch file:
Echo Off
BRK OFF
Echo Executing External Protocol #1
CD\SF\EXTNOD1
DSZ %2 restrict rz %3
CD\SF
BRK ON
Now that SFEXTUPA.BAT, with the above listed commands, resides
in the directory set up as the External Transfer Path, the first upload
External Protocol is successfully configured. The actual contents of
the batch files in use will depend on the specific protocols. The
above is only a sample batch file and should work well with DSZ.
Before the commands in the above described batch file are
explained, it is important to note when a caller selects <B>... from
the upload protocol list, SPITFIRE shells to a batch file named
SFEXTUPB.BAT. As stated before, there are fourteen external protocols
allowed and they are denoted by command letters "A" thru "N". Through
their use, SPITFIRE shells to the corresponding batch files.
A = SFEXTUPA.BAT B = SFEXTUPB.BAT C = SFEXTUPC.BAT
D = SFEXTUPD.BAT E = SFEXTUPE.BAT F = SFEXTUPF.BAT
G = SFEXTUPG.BAT H = SFEXTUPH.BAT I = SFEXTUPI.BAT
J = SFEXTUPJ.BAT K = SFEXTUPK.BAT L = SFEXTUPL.BAT
M = SFEXTUPM.BAT N = SFEXTUPN.BAT
Now, an explanation of these batch files and what SPITFIRE does
in preparation to use them is appropriate and important for the Sysop
to understand.
Page 125
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
When an External Protocol is selected, SPITFIRE does all the
normal tests to be sure it is permissible for the caller to perform
the upload. If all tests were passed, SPITFIRE changes to the
directory configured as the External Transfer Path and stays resident
in memory but shells to the appropriate batch file (as described
above). Keep in mind that SPITFIRE is resident in memory as well as a
second copy of the command processor (COMMAND.COM), consequently the
external file transfer protocol is going to require some memory.
Therefore, the minimum memory requirement of 256 K stated earlier in
the manual, may be insufficient for systems including the external
protocol file transfer options.
Upon performing this shell, SPITFIRE is passing four parameters
to the appropriate batch file. The first parameter is the baud rate.
The second parameter passed is the number of the COMM port being used.
The third parameter is the name of the file to be uploaded. The fourth
parameter is the path in which the file to be uploaded is to reside
(i.e. - C:\SF\UPLOADS). This passed information is needed by most
external file transfer programs and can now be used with DOS batch
commands. The file name is passed in ASCII text as %3. The baud rate is
%1, a number representing baud rate of the caller, such as 2400. The
COMM port %2 is the number of the COMM port being used (1,2,3 or 4).
Sysops who are not familiar with the use of the % command in batch
files should refer to their DOS manual for specific details. The
"restrict" parameter is a feature of DSZ which prevents the uploader
from specifying the file path when uploading to the BBS.
When the external protocol file transfer program has finished
its work, control is automatically returned to SPITFIRE. Once control
is returned, SPITFIRE resets the attributes of all files in the
External Transfer Path (in this instance, C:\SF\EXTNOD1) back to
archive. Then, SPITFIRE changes back to the directory in which the
SPITFIRE system files reside. SPITFIRE now checks to see if the file
that was to be uploaded exists in the File Area in which the uploaded
file should reside, if all went correctly. If SPITFIRE finds the file
in the appropriate File Area, the caller is credited with the upload
and other clean-up chores are performed. SPITFIRE will then
automatically move the uploaded file to the directory the Sysop has
configured as the file upload path (i.e. - C:\SF\UPLOADS). In the
event SPITFIRE does not find the file in the appropriate File Area,
SPITFIRE assumes that the upload was aborted.
Notice that the example batch file (above) has a command to change
to the directory configured as the External Transfer Path. Also notice
that there is a another command to change back to the SPITFIRE system
files directory. These commands do not have to be in the batch files
created because SPITFIRE automatically performs these chores. However,
it is quite permissible for them to be in the batch file so they can
act as a safeguard. Finally, notice a command BRK OFF at the beginning
Page 126
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
of the batch file example, as well as a BRK ON at the end. BRK is a
Shareware utility distributed by Solid Systems of Newport News,
Virginia. It is used to disable and enable the CTRL+BREAK, which can
be used to terminate a batch file. Sysops may need this utility for
the protection of their systems. BRK.ZIP can be downloaded from
Buffalo Creek's BBS.
18.5 EXTERNAL BATCH UPLOAD PROTOCOLS
------------------------------------
SPITFIRE also allows for batch uploads to be transferred with the
use of external protocols, provided the external protocol is written to
include batch upload transfers. Much of the information discussed in
the EXTERNAL UPLOAD PROTOCOLS section of this manual also applies to
External Batch Upload Protocols. However, there are some significant
differences which warrant mentioning.
When creating the SFEXTUP.BBS file, Sysops use a favorite text
editor to list the name of the external batch file protocol that is
available. On the same line, the protocol description is followed by a
comma and the word BATCH. Continuing to use DSZ as an example, the
SFEXTUP.BBS file might now look like this:
<A> ZModem
<B> ZModem Batch,Batch
The SFEXTUP.BBS must reside in the path assigned as the Display
File Path.
DSZ.COM must be placed in the directory configured as the
External File path. Next, using a favorite text editor, a
SFEXTUP<A..N>.BAT file is created which contains the commands
necessary to execute the batch upload. For the above example,
SFEXTUPB.BAT needs to be created to perform external ZModem batch
uploads with SPITFIRE.
The commands for the SFEXTUPB.BAT file should look like this:
BRK OFF
ECHO OFF
ECHO EXECUTING EXTERNAL PROTOCOL # 2
CD\SF\EXTNOD1
DSZ.COM %2 restrict rz
CD\SF
BRK ON
Note, when using DSZ, do NOT list the % file and path parameters on
the command line or it is possible that the uploaded files will end
up with the wrong names. For example, say the caller entered the first
Page 127
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
file name to upload as FILE1.ZIP and the second file to be uploaded
as FILE2.ZIP. Then, rather than sending FILE1.ZIP first, FILE2.ZIP
was sent first and FILE1.ZIP was sent second. FILE1.ZIP would be
named FILE2.ZIP and FILE2.ZIP would be named FILE1.ZIP. However,
the lack of % file parameters allows DSZ to receive more files than
the amount specified by the caller. To overcome this problem,
SPITFIRE creates a simple little text file containing the names of
all files within the External Transfer Path just prior to shelling
to the appropriate batch file. Then when control is returned to
SPITFIRE, it checks the files in the External Transfer directory
against the files listed in the previously created text file. If
additional file(s) are found, and if such file(s) do not already exist
in a File Area, SPITFIRE prompts the caller for a description of
the file. If a description is entered by the caller, then SPITFIRE
moves the file to the appropriate File Area and updates the
SFFILES.BBS. If the caller hangs up or does not enter a description,
SPITFIRE uses the default description, "No Description Provided".
%4 represents the directory the Sysop designated as their upload
directory and %3, %5, %6, %7, %8, %9 are the file names. SPITFIRE
allows up to six files to be uploaded during an external batch upload.
After selecting the batch transfer protocol the caller is prompted
to enter the name of the file to be uploaded and provide a brief
description for each file to be uploaded. The "restrict" parameter
is a feature of DSZ which prevents the uploader from specifying
the file path when uploading to the BBS.
As explained in the EXTERNAL UPLOAD PROTOCOLS section of this
manual, SPITFIRE automatically moves the uploaded file(s) to the
directory the Sysop has configured as the upload file path.
18.6 EXTERNAL BI-DIRECTIONAL FILE TRANSFER PROTOCOLS
----------------------------------------------------
External protocols which support simultaneous uploading and
downloading are referred to as bi-directional protocols. In other
words, having bi-directional file transfer protocols available
enables the BBS to send and receive files at the same time.
Before attempting to explain the installation of bi-directional
file transfer protocols on a SPITFIRE BBS, it may be beneficial to
review how SPITFIRE processes a bi-directional file transfer request.
When a caller initiates a download using a bi-directional file
transfer protocol, SPITFIRE checks the amount of disk space available
and compares it to what the Sysop has configured using the ALT+Z's
Upload Disk Space Requirement option. If disk space is not sufficient
to allow uploads, the caller receives a message which explains,
"...disk space currently prohibits uploads" and the transfer process
is aborted.
Page 128
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Provided the available disk space is sufficient to permit uploads,
the caller is prompted to enter the name of the file to be downloaded.
If the caller has tagged files for downloading, SPITFIRE automatically
defaults in the file name(s) with the name of the file(s) tagged by the
caller. If no files have been tagged, the caller must type in the file
name(s). SPITFIRE will continue to prompt the caller for a file name
until no name is entered.
After completing the download information, SPITFIRE prompts the
caller to enter the file name and file description of the file(s) to
be uploaded. SPITFIRE will continue to prompt the caller for a file
name and description until none is entered. At that time, SPITFIRE
immediately shells to the appropriate batch file so that the file
transfer can begin. When the bi-directional file transfer program is
completed. control is automatically returned to SPITFIRE.
Normally SPITFIRE determines the amount of time a caller should
be compensated for uploads according to the amount of time required
for the transfer process. However it is impossible to determine what
amount time in the bi-directional transfer was spent uploading.
Therefore, at the conclusion of the bi-directional file transfer,
SPITFIRE checks the size of any files which were uploaded, calculates
an approximate upload time and compensates the caller accordingly.
SPITFIRE's support of bi-directional file transfer protocols allows
them to be installed on a SPITFIRE BBS in much the same manner as other
external protocols. HS Link, by Samuel H. Smith, will be used to
explain the process of setting up a bi-directional file transfer
protocol on a SPITFIRE BBS.
To begin, the Sysop will need to use their favorite text editor
to create or modify their existing SFEXTDN.BBS. This is a simple text
file which will contain the names of the external protocols that are
available on the BBS. Each line in SFEXTDN.BBS should contain the
letter A through N which is used by the caller to select the respective
download protocol and the title of transfer protocol (which will
display to the caller). For bi-directional file transfer protocols
these need to be followed by a comma and the term "bi-directional"
(without the quotes). Building on the SFEXTDN.BBS created earlier
(refer to section, External Batch Download Protocols) our sample
SFEXTDN.BBS might look like this:
<A> ZModem
<B> ZModem Batch,Batch
<C> HS-Link Bi-Directional Protocol,Bi-Directional
When the ",bi-directional" is found on a line of the SFEXTDN.BBS,
SPITFIRE automatically assumes a batch mode and a usefile mode. In
other words, you are not required to include a ",batch" or ",usefile"
Page 129
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
on the menu line for bi-directional file transfer protocols. (Refer
the the sections External Batch Download Protocols and Text File
External Batch Download Protocols for further explanation of the
Batch and Usefile features in SPITFIRE.)
Sysops need to place SFEXTDN.BBS in the directory configured as
the Display Files Path. The HS Link executable file (HSLINK.EXE) must
be placed in the directory configured as the External Transfer Path.
To verify, or modify, file paths in SPITFIRE, press ALT+P at the
SPITFIRE "Ready..." prompt. For the purpose of demonstration, an
assumption is being made that SPITFIRE is being run on drive C in a
directory named SF and that the External Transfer file path is
C:\SF\EXTNOD1.
As stated earlier in this documentation, SPITFIRE supports up to
14 external protocols <A..N> to be utilized for downloads. Unlike
other external download protocols which use batch files named
SFEXTDN<A..N>.BAT, bi-directional file transfers are initiated by
batch files named SFEXTBI<x>.BAT. <x> can be any letter A through
N and must match the character which the caller uses to select the
the respective file transfer protocol. In other words, if the
bi-directional transfer protocol is option <A> from the caller's menu
(SFEXTDN.BBS) the batch file would be named SFEXTBIA.BAT, if the
bi-directional transfer protocol is option <E> from the caller's menu
(SFEXTDN.BBS) the batch file would be named SFEXTBIE.BAT, etc. Using
the example above, our sample batch file would be named SFEXTBIC.BAT.
Next, using your favorite text editor, create the appropriate
SFEXTBI<x>.BAT file which contains the commands necessary to execute
the bi-directional file transfer. Using the above example,
SFEXTBIC.BAT needs to be created to perform the HS Link bi-directional
transfers. SPITFIRE will shell to this batch file when a caller
selects <C>... from the download protocol list. The contents of our
sample SFEXTBIC.BAT file might look like this:
@Echo Off
BRK OFF
HSLINK -P%2 @C:\SF\EXT\SFEXTRAN.LST
BRK ON
The actual contents of the batch files in use depends upon the specific
protocol. The above is only a sample batch file that should work well
with HS Link. The bi-directional file transfer protocol batch file
(SFEXTBI<x>.BAT) must reside in your SPITFIRE External Transfer file
path directory after it is created.
Page 130
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
18.7 EXTERNAL PROTOCOL SUPPORT
------------------------------
Configuring the use of external file transfer protocols is
supported by Buffalo Creek Software for registered users of SPITFIRE.
Those who have problems with the external file transfer program
itself are urged to read the documentation and then contact the
author of the program.
19.0 SPITFIRE UTILIZES EMS (Expanded Memory)
--------------------------------------------
Upon boot-up, SPITFIRE automatically attempts to copy
SPITFIRE.OVR to EMS. If there is adequate EMS available, SPITFIRE
will access it from there. This will increase the speed at which
SPITFIRE operates and save wear and tear on the drive. If this is done,
SPITFIRE upon boot-up displays the message "EMS memory is used for
SPITFIRE.OVR".
20.0 SPITFIRE NET-MAIL CAPABILITIES
------------------------------------
SPITFIRE supports net-mail in two basic formats. In the
first format, SPITFIRE is used in conjunction with a front-end
type program where net-mail messages are imported and made available
to callers. SPITFIRE also supports PC Relay style of net-mail which,
when used in conjunction with a Universal Text Interface (UTI) program
will directly import net-mail into SPITFIRE's message base.
Using SPITFIRE with a front-end program requires the use of such
programs as BinkleyTerm or FrontDoor for sending and receiving
net-mail messages. Sysops who run their copy of SPITFIRE with a
front-end type program will have to boot SPITFIRE using the baud rate
of the caller as a command line parameter. For example:
SPITFIRE 2400
NOTE: The SF.BAT file included with the
SPITFIRE package should be used even with
a front-end program. Using the SF.BAT file,
the front-end program should boot SPITFIRE
in this manner - SF 2400. Then within the SF.BAT
file the SPITFIRE command would have to be followed
by a %1. {Example - SPITFIRE %1}
When SPITFIRE is booted in the above manner, SPITFIRE assumes
there is a caller and begins the process of logging the caller on.
Page 131
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
When the caller logs off, then SPITFIRE does not recycle to the
"SPITFIRE ready for use..." prompt but rather terminates so control
can be returned to the front-end program.
It should be noted that if SPITFIRE is used with a front-end
program, the scheduled events feature within SPITFIRE becomes basically
inoperative since events are run while SPITFIRE is at the "SPITFIRE
ready for use..." prompt. However, when used in this environment,
SPITFIRE does check when the caller logs off to see if an event is
scheduled to run.
Certain features within SPITFIRE allow it to be compatible with
specific net-mail drivers.
When configuring the BBS, the Sysop must use the ALT+Z to toggle
their BBS to allow net-mail. In addition, when configuring the
individual Message Conferences the Sysop must toggle the net-mail
option of that particular Message Conference to allow net-mail.
If the BBS and the Message Conference is configured to allow net-
mail, when a caller enters a message, the caller will be prompted
as to whether they wish to send the message via net-mail. If the
caller responds with a Y for Yes, the caller can send a message to
someone who is not a caller on the BBS. Furthermore, the message is
marked as a net-mail message, which allows utilities, such as the
SFUTI<x> listed above, to go through and extract the net-mail messages
for processing and exchange with other BBS systems. The SFUTI<x>
serves as a conversion driver between SPITFIRE and the PC Relay
net-mail software and allows messages transferred between other
BBS systems to be imported directly into SPITFIRE's existing
message base.
21.0 OPERATING A MULTI-NODE SPITFIRE
-------------------------------------
The SPITFIRE Bulletin Board System is fully capable of operating in
a multi-node BBS environment. A multi-node BBS system is one that
allows multiple copies of SPITFIRE to run, having two or more nodes
that share a significant number of the files used during system
operation. When configured for multi-node operation, all nodes of a
SPITFIRE BBS share files contained in the WORK, MESSAGE and DISPLAY
file paths. The SYSTEM and EXTERNAL protocol file paths must be set up
individually for each node.
21.1 MULTI-NODE BBS REQUIREMENTS
--------------------------------
In order to operate SPITFIRE in a multi-node environment, the Sysop
must either be using a multi-tasking software or have multiple computer
systems networked together. Under most circumstances, each node the
Page 132
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Sysop wishes to install will require its own telephone line and modem.
The exception to this being, if in either the multi-tasking or network
environment, the Sysop configures a copy of SPITFIRE BBS with a
maximum baud rate of 0 (making that node only accessible by local
logons).
21.2 CONFIGURING SPITFIRE FOR MULTI-NODE OPERATION
--------------------------------------------------
In general, SPITFIRE is configured much the same for multi-node as
it is for a single node system. (Refer to the GETTING STARTED section
of this manual for more detailed information.) However, there are
several configuration options the Sysop must be sure to set correctly
when installing or expanding to a multi-node system.
To begin, press ALT+Z to open SPITFIRE's configuration window.
Modifications must be made so that a node number is assigned for the
individual node being configured and the total number of available
nodes entered. Also, it is possible to configure one or more of the
available nodes as a private BBS. If this is done, be sure to use the
ALT+Z option to set the security required for accessing the private
node being configured. For any node not configured as a private BBS,
simply have the security required set to zero. These settings need to
be appropriately configured for each node on the system.
In addition, when operating SPITFIRE in a multi-node environment,
the DOS SHARE program is normally required to be used. This can be
accomplished by placing SHARE in the AUTOEXEC.BAT so SHARE is loaded
each time that the computer is booted.
21.3 FEATURES UNIQUE TO MULTI-NODE OPERATION
---------------------------------------------
When operating a multi-node SPITFIRE BBS system, one of the options
available from the Main Menu is <W>...Who On. If a caller selects this
option, information is displayed to the screen telling the caller of
anyone else who is simultaneously logged on to any of the other
available nodes. The information of who is on the various system nodes
is stored in SFWHOSON.DAT, which resides in SPITFIRE's Work File Path.
Several features unique to the multi-node SPITFIRE environment
relate to packing the message base or caller's file. It is extremely
important that there is no other BBS activity during the packing of
these files. Therefore, certain safeguards are included in SPITFIRE
which monitor activity on all nodes to prevent system access when
packing of these files is in progress. Similarly, SPITFIRE will not
allow these files to be packed if there is activity on any of the
available nodes.
Page 133
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SPITFIRE does not allow a Sysop to use the internal SPITFIRE
commands for packing the caller file or packing the message base while
a caller is logged on one of the other nodes. If the Sysop attempts
this, the following message will be displayed: "Sysop, you are not
allowed to pack the caller's file/message base while other nodes are
busy." Depending upon which activity is trying to be performed, either
the text of caller's file or message base will display in the above
message.
If a caller attempts to log onto the system when SPITFIRE is
packing the message base or caller's file, SPITFIRE displays the
following message, "A maintenance operation is presently being
performed! Please call back in a few minutes." Upon logging on
the caller is shown the SFPRELOG.BBS and the WELCOME1.BBS/CLR but after
entering their name and password the above message will be displayed.
Sysops may create their own screen for displaying the maintenance
message if preferred. This screen, SFMAINT.BBS/CLR displays
immediately after the caller enters their name, replacing SPITFIRE's
default message mentioned above.
If configured as a multi-node system, when booted, SPITFIRE checks
to determine whether maintenance is being performed (packing the
callers file and packing the message base). In the event SPITFIRE
discovers that maintenance is being performed, the following message
is displayed:
Report - Maintenance Being Performed.
Pausing Until Maintenance Is Complete.
Press Any Key To Return To DOS.
SPITFIRE then goes into a loop and continues to check the
maintenance status indefinitely until the maintenance has been
completed. When the maintenance is completed, SPITFIRE continues
initialization and waits for a caller. During the time while SPITFIRE
is doing the continuous maintenance check loop, if a key is pressed
SPITFIRE terminates and returns to DOS. In other words, when booting
SPITFIRE, if it is discovered that maintenance is being performed by
another node, SPITFIRE loops until the maintenance status changes or
until the Sysop presses a key to return to DOS.
21.4 NODE CHAT
--------------
On a multinode SPITFIRE v3.3 BBS, callers are able to chat with
callers on another node via the Node Chat feature. This feature is
accessed via the "<W>ho's On The Other Node?" Menu Selection which is
found on the Main Menu.
Page 134
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Configuring Node Chat
---------------------
To set up Node Chat, the Sysop may need to edit DAILYLMT.DAT. Node
Chat parameters are specific to each security level. The default values
allow for five Node Chats of five minutes each per day. To set
specific values for a given security level, the following parameters
(preceded by ONE comma) may be appended to any security level's entry
in DAILYLMT.DAT:
#OCA=(Number Of Node Chats Allowed Each Day)
TPNC=(Time In Minutes Permitted For Each Node Chat)
An example DAILYLMT.DAT might look like this:
4,MPC=0,MPD=0,DLPD=0,#OCA=0,TPNC=0 (Zero Permitted, Zero Minutes)
5,MPC=30,MPD=30,DLPD=10,KB=2000 (Default Number And Time)
10,MPC=60,MPD=60,DLPD=15,KB=5000,#OCA=10,TPNC=20
(10 Chats Daily, 20 Minutes Each)
20,MPC=60,MPD=60,DLPD=15,KB=5000,TPNC=30
(Default Number, 30 Minutes Each)
30,MPC=60,MPD=60,DLPD=15,KB=5000,#OCA=20
(20 Chats Daily, Default Time)
To use default values for both Number Of Chats Daily and Time Per Chat
for ALL security levels, no changes need to be made to DAILYLMT.DAT.
* It is REQUIRED that ALL nodes on a multinode SPITFIRE BBS have *
* a common WORK directory in order to be available for Node Chat! *
Initiating Node Chat
--------------------
When a caller selects "<W>ho's On...", they are presented with a
summary of activities on the other nodes. Callers on the other nodes
are NOT available for Node Chat under the following circumstances:
* when they are chatting with the Sysop (Local Chat)
* when they are using a Door
* when they are already in another Node Chat
* when they are reading or entering messages
* when they are involved in the transmission of files
* when they are listing files
* when they are logging onto the BBS
* when those of Sysop-Level Security are using Sysop Utilities
The caller desiring the Node Chat sees something like this:
Page 135
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
" Checking other nodes, please stand by...
Node 1 - (1st Caller) ................... Available for chat!
Node 2 - (2nd Caller) ................... Available for chat!
Node 3 - Busy Caller ................... Transmitting file!
(1st Caller), would you like to initiate a Node Chat? <y/n> "
A <y>es response then asks the caller:
" Chat with which node # "
If the caller who desires a node chat enters a valid node number, the
caller on the desired node is notified that a Node Chat with them is
requested and by whom. They then see something like this:
" (2nd Caller) would like to chat!
Would you like to chat with (1st Caller)? <y/n> "
while the first caller sees:
" Awaiting other node response...Press ESC to abort! "
If the chatted caller agrees to chat, Node Chat occurs. If the chatted
caller does not want to chat, the caller who requested the chat is
returned to the BBS after a short period of time. They are free to
request another Node Chat later or attempt to chat with another node.
Node Chat Procedure
-------------------
Once a Node Chat request is agreed upon and both callers are
connected, the caller who requested the chat is presented with the
following:
" Establishing connection...please stand by...
CTRL+X to exchange chat control when at "CHAT:"
ESC to terminate chat!
Hello, (1st Caller)! What can I do for you?
CHAT: "
while the chatted caller is presented with the prompt:
" Establishing connection...please stand by...
WAIT: "
Only the caller who is at the "CHAT:" prompt may type. SPITFIRE's Node
Chat feature sends typed text to the other node and word wraps
text that spans more than one line. When the chatting caller has
finished their thought and wishes to switch control to the other
Page 136
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
caller, control of the chat may be exchanged by hitting <CTRL+X>.
Doing so presents the "CHAT:" prompt to the other caller while
the first caller switches to the "WAIT:" prompt. At that time, the
second caller may type.
In order to terminate Node Chat and return to other activities,
either caller may hit <ESC>. This shortly ends the Node Chat and
returns both callers to the section of the BBS that they were in before
the Node Chat began. If either caller drops carrier for any reason,
the Node Chat is terminated and the other caller is returned to the
BBS.
22.0 SPITFIRE MULTI-TASKING/NETWORK ENVIRONMENT
------------------------------------------------
In order to operate a multi-node SPITFIRE BBS system, SPITFIRE
must be configured to run in either a multi-tasking or networked
environment. In a multi-tasking environment multiple copies of
SPITFIRE need to be loaded on one computer with the aid of such
multi-tasking programs as Windows 3.X or DESQview. In a networked
environment individual copies of SPITFIRE need to be loaded on any
number of computers that are networked together via such networking
systems as LANtastic. The following sections discuss the procedure
for installing SPITFIRE in such environments.
23.0 SPITFIRE TECHNICAL REFERENCE INFORMATION
---------------------------------------------
There are absolutely no plans whatsoever to release the source
code for SPITFIRE. However, we do feel some information may be of use
to our Sysops to help them understand how SPITFIRE works. If there is
something you would like to know which is not covered in this
documentation, please ask via Buffalo Creek's BBS (515)-225-8496.
We will make the information available to you, if possible.
There is certain information that is required for those interested
in writing utilities and other third party type programs for SPITFIRE.
If such an instance, please contact Buffalo Creek's BBS for information
regarding record structure information needed. We will make the
information available to you, if possible.
When a caller goes through a Door or uses any of the Sysop
configurable features available from each menu, SPITFIRE creates
a simple text file named SFDOORS.DAT, SFMAIN.DAT, SFMESS.DAT or
SFFILE.DAT in the SPITFIRE HOME directory. This text file contains
necessary information for the caller to return to SPITFIRE. The
text file is erased when control is returned to SPITFIRE.
Page 137
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
24.0 SPITFIRE COMPANION PROGRAMS
---------------------------------
Several SPITFIRE companion programs are included within the
SPITFIRE distribution package. These programs are designed to
work with SPITFIRE. Those which are optional and work independently
of SPITFIRE are noted as so with (OPTIONAL) after the utility name.
It is the intention of Buffalo Creek Software to provide these programs
with SPITFIRE and hopes they are found to be assets in the operation of
a SPITFIRE BBS.
Some of these programs are shelled to during the execution of
special features within SPITFIRE and are noted as such with (SHELL)
after the program name. Of these, some may also be executed
independently of SPITFIRE as well. This will be noted in the
individual program description.
It should be noted that the following programs all contain
individual documentation that should be referred to for complete
details. Any of these programs may be updated prior to the next
SPITFIRE release without written notification. Therefore, it is
recommended that you call Buffalo Creek's BBS periodically to check
for updated versions of these programs.
24.1 DAILYLMT (OPTIONAL)
------------------------
DAILYLMT provides an easy to use menu program for creating or
editing SPITFIRE's DAILYLMT.DAT file. It easily allows SPITFIRE
Sysops to add, change or delete security levels within DAILYLMT.DAT.
In addition, an option is provided for the Sysop to review the contents
of the existing DAILYLMT.DAT file. The responses to DAILYLMT's prompts
set the minutes per call, minutes per day, downloads per day, quick
log-on status, kilobytes per day, number of chats allowed, time per
node chat, violation warning ratio and violation enforcement ratio
for each security level. DAILYLMT uses the information that
has been input to format individual lines in the DAILYLMT.DAT file.
24.2 SFDOOR (OPTIONAL)
----------------------
SFDOOR is a SPITFIRE utility that is used to create and or modify
SPITFIRE's SFDOOR.MNU file. SFDOOR is menu driven for ease of use and
aids the Sysop in installing or deleting door programs on a SPITFIRE
BBS. SFDOOR also provides an option for reviewing the current
SFDOOR.MNU file. When adding or changing the SFDOOR.MNU file, Sysops
provide information regarding the title for the door's name; whether
the security will be greater than or equal to, equal to, or less than;
and the security level required to access the door. SFDOOR will
then update the SFDOOR.MNU file accordingly.
Page 138
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
24.3 SFSENDIT (OPTIONAL)
------------------------
SFSENDIT is a SPITFIRE utility that is used to flag files for
sending to a specific caller or group of callers with a common security
level. The file flagged for sending must exist in a SPITFIRE File Area
although it need not be listed in the SFFILES.BBS. SFSENDIT stores
the file area and the file name in the SFUSERS.DAT file. When the
caller next logs on the BBS, he/she is notified that the file is
there for them to download.
SFSENDIT is a limited to flagging one file per caller or group of
callers with a common security level. Similar utilities exist that
offer more complex file flagging schemes. If SFSENDIT does not meet a
Sysop's needs, they may wish to use one of these other utilities.
However, it should be mentioned that it is possible for SFSENDIT to
send more than one file at a time by compressing the desired files
together into one file. Also, SFSENDIT does not work when a caller is
logged on locally. If the file to be downloaded is in a free file
area, the caller's statistics are not updated. If the file downloaded
is in a non-free file area, the caller's download statistics will be
adjusted.
SFSENDIT is menu-driven and easy to use. SFSENDIT provides
options for flagging a file for download by caller or security level,
removing flags by caller or security level, and viewing flags set
by caller or security level.
24.4 LAKOTA (SHELL)
-------------------
LAKOTA is a SPITFIRE utility which allows the caller to download
messages in QWK format. Using a QWK offline reader, the caller can
read messages, reply to messages and/or enter messages offline. The
compressed reply packet (in QWK format) can then be uploaded with
LAKOTA the next time the caller logs on the BBS. LAKOTA will insert
messages contained in the reply packet into SPITFIRE's message base.
When downloading the caller is given the option of downloading
messages to the caller or all new messages. The caller is also
asked to specify which conferences the messages to be downloaded
will be extracted from. Conference options include All Conferences,
Select A Conference or Your Queued Conferences. Once the selection
is defined, LAKOTA creates the QWK mail packet and compresses it in
ZIP format. Next, if the caller is logged on locally the message
packet is placed in the SPITFIRE home directory. If the caller is
logged on remotely they are prompted to select a file transfer
protocol to be used in the message download. If the download is
successful the caller is then prompted as to whether they wish to
have their message pointers updated.
Page 139
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
When uploading the reply packet, if the caller is logged on
locally, LAKOTA will prompt the caller to enter the drive, path
and file name of the mail packet to be uploaded. When logged on
remotely, the caller is presented with a menu that allows them to
select a file transfer protocol to be used in the message upload.
The messages from the uploaded packet are then inserted into
SPITFIRE's message base.
LAKOTA is a simple, get-the-job-done QWK mail upload/download
program. There are a number of similar mail doors which offer
more complex options for exchanging mail on a BBS. If LAKOTA
does not meet a Sysop's needs, they can choose other mail exchange
utilities. If you do not wish to have this option available to
callers, the security of the SFMSG,MNU for this feature should
be set high enough so the caller cannot access it.
LAKOTA must be used with SPITFIRE and cannot be executed
independently of SPITFIRE.
24.5 SFPCKUSR (SHELL)
---------------------
SFPCKUSR is a SPITFIRE companion utility which is used to
purge the caller's record from the caller data base, SFUSERS.DAT.
SPITFIRE will shell to SFPCKUSR when Pack Users File is selected
from the Sysop Menu. SFPCKUSR can also be used independently of
SPITFIRE.
When the Sysop selects the Pack User File from the Sysop
Menu, the Sysop is prompted whether inactive callers should
be purged. If the Sysop responds with a Y, the Sysop is
then asked to enter the number of days to be used for purging
inactive callers. If the number of days between today's date
and the caller's last log on is greater than the number of days
the Sysop enters here, the caller is considered inactive and will
be purged. Once these questions have been answered, SPITFIRE
shells to SFPCKUSR, passing the purging criteria to it. SFPCKUSR
will purge any callers who have been marked for deletion and if
the inactive purge has been selected, any callers who have not
called for the amount of days specified by the Sysop will also
be purged. Once SFPCKUSR has completed the purge process, a list
of the callers who were purged is written (or appended to)
SFPURGED.USR in the WORK directory and control is returned to
SPITFIRE.
SFPCKUSR can also be used independently from SPITFIRE. When
initiated from the DOS prompt or from within a batch file without
Page 140
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
any command line parameters, only callers who have been marked for
deletion will be purged. Command line parameters can be used to
specify the number of days for purging inactive callers. When
SFPCKUSR has completed the purge process, a list of the callers
who were purged is written (or appended to) SFPURGED.USR in the
SPITFIRE WORK directory.
24.6 SFPCKMSG (SHELL)
---------------------
SFPCKMSG is a SPITFIRE companion utility which is used to
pack the message base. The Sysop can control which messages
are packed according to the following criteria: number of days
old, threaded messages, unreceived messages. The criteria
can be set independently for each Message Conference available
on the BBS.
When Event M is activated, SPITFIRE will shell to SFPCKMSG
to pack the message base. When the Sysop elects to use the
Pack Message Base option from the Sysop Menu, SPITFIRE will
shell to SFPCKMSG to pack the message base. When SPITFIRE
shells to SFPCKMSG the settings on the Message Conference
record for each conference are used to determine the criteria
for purging messages from the system.
SFPCKMSG can also be used independently of SPITFIRE. If
you choose to use SFPCKMSG from the DOS prompt or from within
a batch file, command line parameters are available to define
the criteria for which messages will be purged from the system.
25.0 COMMENT FROM THE AUTHOR
-----------------------------
Undoubtedly there are features that can be added to SPITFIRE.
Your suggestions and comments will be considered for future releases,
however, you must realize that not all ideas will or can be
implemented. SPITFIRE was designed, written and is upgraded with
a simple, small, fast, get-the-job-done BBS package in mind (the KISS
system). SPITFIRE will more than do the job for you. However, plans
are already in the making for improvements and additions. Hopefully,
with your help, SPITFIRE will continue to improve without the loss of
its simplicity.
There were many people who offered suggestions and discovered
problems during the development of SPITFIRE. It would be nice to list
the names of those people but surely I would leave someone out. I do,
however, feel it important to make note that Jacque Shipley kept track
Page 141
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
of all the changes and improvements in SPITFIRE version 3.3 and
spent a tremendous amount of time revising the manual. Further, I
thank Jeff Kerry, Brent Morris, Jay Jackson, Rick Fournier, Armand
Michaud and Larry Wagoner for proof-reading this manual.
As mentioned earlier, SPITFIRE is written in Borland's Turbo
Pascal. This entire program was written by yours truly (Mike Woltz).
It has taken over five years to get SPITFIRE to this point
(maybe I'm slow). This opportunity is taken to thank my wife Ann,
my children Mason, Jesse & Amanda and my grandson Joshua for
tolerating the countless number of hours that were spent writing
and testing SPITFIRE. Lord knows, I could be a better husband,
father and grandpa. Most important, I thank God for giving me the
ability to write SPITFIRE.
This opportunity is taken to thank each Sysop who has gone to
the expense of registering SPITFIRE. I have had the pleasure of
meeting and working with thousands of people in my life. I think
I am safe in saying that for the most part, SPITFIRE Sysops are SUPER,
top-shelf people. Without these Sysops' support, patience,
cooperation, etc., none of this would be possible.
I would like to mention one last thing that has become a concern
to me. After putting over five years of my life into SPITFIRE, I
have attempted to keep the cost of this software as reasonable as
possible. I have noticed lately that there are many third party
utilities, etc. being written for SPITFIRE and I have also noticed
that in some cases the registration fee for these utilities is nearly
half the cost of SPITFIRE. It doesn't seem right to charge $20.00 to
$35.00 for a SPITFIRE utility that can be written in a day or two and
I would ask those authors to attempt to keep their prices comparable
to the SPITFIRE project. No rip-offs, OK? Thank you!
Page 142
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
NOTES:
Page 143
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
APPENDIX A
----------
MODEM INITIALIZATION STRINGS
----------------------------
The following list contains a listing of modem models and their
corresponding initialization string which have been reported to
to work with SPITFIRE Bulletin Board Systems. Buffalo Creek
Software includes this list in hopes the information may prove
beneficial to other Sysops. In addition to this list, updated
text files which group reported initialization strings by modem
manufacturer are available for download from Buffalo Creek's BBS.
Examples of such files include BOCA.TXT, PP.TXT, SUPRA.TXT, etc.
MODEM MODEM INITIALIZATION STRING
-------------------------------------------------------------------
96 Fax/Modem 2400..........................ATS0=0Q0V1E0M0H0S2=1X1^M
ACEEX Fax 9624 Internal 9600 {MNP5}.....ATS0=0Q0V1M5&C1E0H0S2=1X1^M
ACEEX 2400..................................ATS0=0Q0VE0M0H0S2=1X1^M
ATI...................................AT&F2S0=0S2=1&C1&D2E0Q0V1W2^M
ATI 2400 ETC MNP1-5.........AT&Q5&C1&U1&D0&T5M0H0W1X5V1E0S2=1S0=0^M
ATI 2400 ETC..................AT&F1&B0&C1&D0&T5M0H0V1E0X2S2=1S0=0^M
ATI 9600 ETC..........AT&F2W2&C1&D2S0=0S2=1S7=100&W0&Y0Q0E0H0M0X6^M
Alpha Concord 1200.........................ATS0=0Q0E0M0V1H0S2=1X1^M
Amstrad MC 2400......................ATS0=0Q0V1E0M0H0S2=1X2&C1&D0^M
Amstrad PPC Internal 2400............ATS0=0Q0V1E0M0H0S2=1X2&C1&D0^M
Anchor..(External 2400).............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0^M
Anchor..(Internal 2400)....................ATS0=0Q0V1E0M0H0S2=1X4^M
Anchor..(Internal 2400).............AT&C1&D2&T5M0H0X4V1E0S2=1S0=0^M
Avatex 1200 HC.............................ATS0=0Q0V1E0M0H0S2=1X1^M
Avatex 1200I........................ATX1E0M0H0V1S0=0S1=1S9=1S10=2^M
Avatex 2400 External.............ATS0=0Q0V1E0L0M0&D0&C1X1H0S2=1&W^M
Avatex 2400II..............................ATS0=0Q0V1E0M0H0S2=1X1^M
Bit Blitzer 2400................AT&C1&D2E0V1M0S2=1S0=0S6=1S10=1X1^M
Boca.................................AT&C1&D2S0=0Q0V1E0M0H0S2=1X1^M
Boca..............................AT&FE1V1X4&C1&D2S0=0S7=60S95=44^M
Boca........................AT&FE1V1X4&C1&D2S0=1S2=1M0S7=60S95=43^M
Boca.........................ATS0=0&K3&Q0B0Q0V1E0M0H0S2=1S95=47X1^M
Boca........................AT&FE1V1X4&C1&D2S0=0S7=30S2=1S95=44W2^M
Boca 14400....................ATS0=0&K3&Q0B0Q0V1E0M0H0S2=1S95=1X1^M
Boca Internal...................AT&FE1V1X4&C1&D2S0=0S7=30S95=44W2^M
BSM Quick Comm................................AT&F*Q0S2=1E0M0H0&W^M
CMP 2400.....................................ATS0=0Q0E0M0H0S2=1X4^M
CVI Internal 2400 Baud.....................ATS0=0Q0V1E0M0H0S2=1X1^M
Capetronics MD 1207...1200 Baud..............ATE0V1Q0M0S2=1S0=0X1^M
Capetronics...........1200 Baud............ATV1E0Q0M0H0S0=0S2=1X1^M
Cardinal...................................ATS0=0Q0V1E0M0H0S2=1X1^M
Cardinal............AT&C1&D2&T5M0V1W2X4S0=0S2=1S10=36S46=136S95=2^M
Page 144
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Cardinal 2400.......................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0^M
Cardinal 2400 MNP.....................AT&C1&D2\Q3\N3\J0\C1\V1S0=0^M
Cardinal v.32 9600.....ATS0=0&C1&D3&M6&B1&T5V1X4Q0M1H0E0S2=1S46=7^M
Commstar 2400..(Internal)..................ATS0=0Q0V1E0M0H0S2=1X4^M
Compaq Internal 2400........................AT&F&C1&D2&B1V1S2=1&W^M
Complete Communicator............................ATE1Q0V1X4&C1&D2^M
Compucom Speedmodem Combo................AT&F2*H2%C0H0S0=1&D2X4&W^M
CompuCom Speedmodem Combo (modem/fax)
AT&F2*H2%C1S0=0S2=1&C1&D2\C1Q0V1E1M0H0X4&W^M
CompuCom Speedmodem Combo 19200
AT&F2*H2%C1S0=0S2=1&C1&D2\C1Q0V1E1M0H0X4&W^M
CompuCom SpeedModem Champ 14400
AT&F2*H2%C0S0=0S2=1&C1&D2V1Q0M0X1H0&W^M
Computer Peripherals 2400..................ATS0=0Q0V1E0M0H0S2=1X1^M
Computer Peripherals Hook-up 2400s.......AT&FS0=0Q0V1E0M0H0S2=1X4^M
Dallas Fax.........................ATS0=0&F&C1&D3W1Q0E0M0H0S2=1X4^M
Dallas Fax........AT&FS=QV1X4&C1&D3S95=2W1&K3S36=7&Q5S46=138S48=7^M
Digicom 9624LE........................ATS0=0*F3*E9E0V1M0S2=1X4&N6^M
Evercom 24E................AT&C1&D0&T5M0H0X1V1E0S2=1S0=0\N3\V1\C1^M
Everex 24 (Internal 2400)...........AT&C1&D0&T5M0H0X1V1E0S2=1S0=0^M
Everex Internal 1200.......................ATS0=0Q0V1E0M0H0S2=1X1^M
Everex (Internal 2400)..............ATM0E0V1H0X1&D0&T5&L1S0=0S2=1^M
Everex Internal 2400 MNP 5...AT\N3\Q3\V1\G1\J0%C1&C1&D2X4S2=1S0=0^M
Fastalk 2400..(External)...................ATS0=0Q0V1E0M0H0S2=1X1^M
Fastcomm 9696.v32.............ATS0=0S2=1S10=2&H1&I1&M4V1M0X1#X1&W^M
FastComm HSD 9642T V32V42 9600
ATE0M0Q0V1&H1&I1&C1&D3&M4&N0&U0&Q6#X1S46=9W2S0=0S2=1H0X4&W^M
Franklin FM-2400E..........................ATS0=0Q0V1E0M0H0S2=1X1^M
Galaxy Networks 38400..........ATS2=1H0S0=0M3V1E0X4Q0&D0W2\V1\Q3:^M
Gateway 2000 Telepath Fax/Modem.....ATS0=0Q0V1E0M0W2S2=1&C1&D2&Q8^M
GVC External 2400..............................ATS0=0V1E0M0S2=1X1^M
GVC Internal 2400................ATS0=0&C1&D2Q0V1E0M1L3H0S2=1X4&W^M
GVC v32 v42..............ATE0H0M0Q0X4V1S0=0S2=1S10=75\Q2\N6\V1&D0^M
GVC 9600 V.32/V.42.....................AT&C1&D2%C1\Q3\J1\N6\V1\L1^M
GVC........................................ATS0=0Q0V1E0M0H0S2=1X1^M
GVC......................................ATS0=0V1S2=1%R1\X0\61\T0^M
GVC Super 9600..........................TB2&C1&D2M1V1E1Q0S2=1S0=0^M
GoldStar GSM2400 (External).............ATS0=0Q0V1E0M0H0S2=1X1&C1^M
Hayes 1200..(External).....................ATS0=0Q0V1E0M0H0S2=1X1^M
Hayes 1200..(Internal).....................ATS0=0Q0V1E0M0H0S2=1X4^M
Hayes 2400..(External)..............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0^M
Hayes 2400..(Internal).....................ATS0=0Q0V1E0M0H0S2=1X4^M
Hayes 2400.................................ATS0=0Q0V1E0M0H0S2=1X1^M
Hayes 2400..........................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0^M
Hayes OPTIMA 9600 Smartmoden
ATS0=0&C1&D2&Q5&K3&R1M0Q0V1E0H0S2=1X4^M
Hayes Personal.........................AT&C1&D2S0=0H0Q0V1E0S2=1X1^M
Hayes v96..................................ATS0=0Q0V1E0M1H0S2=1X1^M
Hayes Ultra 9600
ATS0=0S95=2N1W2X4&C1&D2&K3&Q5&R0V1Q0L2S2=1S36=7^M
Page 145
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Hook-up 2400S..............................ATS0=0Q0V1E0M0H0S2=1X4^M
Hook-up 2400...............................ATS0-0Q0V1E0M0H0S2=1X1^M
IBM Model 5842 2400........................ATS0=0Q0V1E0M0H0S2=1X1^M
Infotel...............................ATS0=0Q0V1E0W2H0S2=1X4S95=2^M
Intel...............................AT&C1&D2%E0\N3\Q3\J0\V2X4E0V1^M
Intel....................................ATS0=0QV1E0M0H0S2=1X1%C0^M
Intel.............................................AT&F%C0S0=0S2=1^M
Intel (Highspeed)....................ATS0=0&C1&D2Q0V1E0M0H0S2=1X4^M
Kyocera KM1200D............................ATS0=0Q0V1E0M0H0S2=1X1^M
Laser 2400.................................ATS0=0Q0V1E0M0H0S2=1X1^M
Leading Edge 2400...................AT&C1&D2&T5M0H0X1V1E0S2=1S0=0^M
Lightcom......................AT&F&C1&D2S0=0Q0V1E0M1H0S95=3S2=1X1^M
LightCom...............................AT&FE0&C1S2=1S95=2N1W2\T15^M
Lightcom 144F.............................AT&F&C1&D2E0W1S2=1S38=0^M
Magitronic MB2450..(Internal)..........AT&C1&D2M0H0X1V1E0S2=1S0=0^M
Megatronics - Internal 2400................ATS0=0Q0V1E0M0H0S2=1X4^M
Microcom QX/V.32c.................ATM0&C1S0=0V1E0H0S2=2X1\N0-Q2&W^M
Mikon Super Modem (2400 External)..........ATS0=0Q0M0V1E0S2=1X1&W^M
Motorola 2400..................ATS0=0Q0V1EM0Hos2S10=1X1&C1&D2*MR1^M
MultiTECH V32
AT&E1&E4&E7&E12$BA0$MB9600$SB19200S0=0S2=1V1M0H0&Q1^M
MultiTech MultiModem V32...............AT&C1&D2M0X1V1E0Q0S2=1S0=0^M
Multitech 224EC (2400 Internal)............ATS0=0Q0V1E0M0H0S2=1X1^M
NEC N2420/30HN.............................ATS0=0Q0V1E0M0H0S2=1X6^M
Netcomm 1234SA Datalock 2400....AT&C1&D2E0V1M0S2=1S0=0S6=1S10=1X1^M
OKITEL..............................ATS0=0\C2E0\J1\N3\V1\Q3S2=1X1^M
Omnitel Encore 2400 HB...............AT&F&C1&D2M0H0X1V1E0S2=1S0=0^M
Packard Bell 1200..........................ATS0=0Q0V1E0M0H0S2=1X1^M
Packard Bell 2400 Internal.........ATS0=0&C1&D2Q0V1E0M0H0S2=1X4&W^M
Packard Bell............ATS0=0&C1&D3&M0&B0T5V1X4Q0M1H0E0S2=1S46=7^M
Packard Bell...............................ATS0=0Q0V1E0M0H0S2=1X1^M
PC Logic..........................ATS0=0V1Q0N1M0&C1&D2&Q9S95=34W2^M
Penril 2400 DataLink.......................ATS0=0Q0V1E0M0H0S2=1X1^M
Practical Peripheral (Int 2400)...AT&C1&D2M0H0X1V1E0S7=30S2=1S0=0^M
Practical Peripheral 2400....................ATS0=0Q0V1E0H0S2=1X1^M
Practical Peripheral 1200 Baud.............ATS0=0Q0V1E0M0H0S2=1X1^M
Practical Peripherals........................ATE0V1Q0M0S2=1S0=0X1^M
Practical Peripherals.........................AT&F1&Q9E0M0S95=3W2^M
Practical Peripherals.................AT&F1&C1&D3X4W2S2=1S0=0M0V1^M
Practical Peripherals.....................................AT&F1&W^M
Practical Peripherals....................AT&F&C1&D2V1X1M0S0=0S2=1^M
Practical Peripherals 14400............ATS7=45S0=0V1X4&C1&D2&Q5W2^M
Prentice Popcomm 2400 (c200)........AT&C1&D2&T5M0V1E0Q0X1S2=1S0=0^M
Prentice 2400..............................ATS0=0Q0V1E0M0H0S2=1X1^M
Prometheus ProModem 2400 B/2...............ATS0=0Q0V1E0M0H0S2=1X4^M
Prometheus 2400........................ATE1V1X3X4Q0&C1&D2S2=1S0=0^M
QBlazerby Telebit.......................ATS0=0V1S58=2E0M0H0S2=1X1^M
Quicktel...................................ATS0=0Q0V1E0M0H0S2=1X1^M
Scout-Plus..............................ATS0=0&B1M0Q0V1E0H0S2=1X4^M
Page 146
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Smart One..(Best Data Products of CA)......ATS0=0Q0V1E0M0H0S2=1X1^M
SmartLink (2400 External)................ATE1X1V1Q0M0H0S0=0S2=1&W^M
Smartlink................................. ATS0=0Q0V1E0M0H0S2=1X1^M
SmartOne 2400........................ATS0=0Q0V1E0M0H0S2=1X1&C1&D2^M
Smarteam.....................................ATS0=0V1E0M0H0S2=1X1^M
Supra 2400.................................ATS0=0Q0V1E0M0H0H2=1X1^M
Supra 2400 MNP Internal..........................AT&F2%C\C1M0S2=1^M
Supra 2400 External..................ATS0=0&C1&D3L3M1V1S2=1E0H0&W^M
Supra...................................AT&F2S0=0Q0V1E0M0H0S2=1X1^M
Supra......................AT&F2S95=3W2S2=125S12=25S0=0X4V1&C1&D2^M
Supra......................................AT&F2S0=0W2S2=1S95=2H0^M
Supra Fax..........ATS0=095=2N1W2X4&C1&D2&K3&Q5&R0V1Q0S2=1S36=7H0^M
Supra Fax................................ATS0=0Q0V1W2E0M0H0S2=1X4^M
SupraModem2400 I...........................ATS0=0Q0V1E0M0H0S2=1X4^M
SupraModem 2400 Plus v.32/v.43.......AT&F2\V2S0=0Q0V1E0M0H0S2=1X1^M
Tandy 2400..............................ATS0=0Q0&D2V1E0M0H0S2=1X1^M
Telenetics.............................ATM1V1X4&C1&D2L1S7=60S1155^M
Telepath modem from Gateway.........AT&Q9&D2&K3&T5M0W1S95=5S2=1X4^M
Tempo Everex 9600..........................ATS0=0Q0V1E0M0H0S2=1X1^M
Twimcom....................ATS0=0E0&C1&D2&T5M0V1Q0X152=1S0=0U2\N0^M
Twincom....................................AT&C1&D2X4M1L2V1E1S0=0^M
Twincom..............................ATS0=0Q0V1E0M0W2S2=1X1&C1&D2^M
Twincom 14400..........ATS0=0V1&C1&D2&Q5N1W1S38=1S2=1E0M0H0Q0X4&W^M
Twincom v32/42i......................ATS0=0Q0V1E0M0W2S2=1X1&C1&D2^M
Twincom 38400 v.32/42i...............ATS0=0Q0V1E0M0W2S2=1X1&C1&D2^M
US Robotics Courier 2400...................ATS0=0Q0V1E0M0H0S2=1X1^M
USR Courier HST 14400..........ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6^M
US Robotics HST 9600......(9600 Baud)......ATS0=0Q0V1E0M0H0S2=1X1^M
USR Sportster.........AT&F&C1&D2&Q5S48=7S36=7S0=0S2=1X4V1M0H0W2Q0^M
USR Sportster.............ATS0=0&B1&N0&H1&R1&Y1B0Q0V1E0M0H0S2=1X4^M
US Robotics Sportster...............AT&C1&D2&T5M0H0X1V1E0S2=1S0=0^M
USR HST 9600..(19200 Baud).....ATS0=0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6^M
US Robotics Dual Standard (v32bis/v42bis)
ATS0=0&B1&H1&K3&N0&R2&Y3B0Q0V1E0M0H0S2=1X6^M
USR Dual Standard 38400......ATS0=0B0&B1M0&H1&R1&Y1Q0V1E0H0S2=1X6^M
USR 14.4 D/S..............ATS0=0B0&B1&N0&H1&R1&Y1Q0V1E0M0H0S2=1X6^M
VIVA 2400m External MNP5....ATH0Q0V1E0M0S0=0S2=1X1&C1&D2\N3\Q3\V1^M
VIVA 2400 MNP External...........................AT&F2%C\C1M0S2=1^M
Zoom 2400 Internal Modem...................ATS0=0Q0V1E0M0H0S2=1X4^M
Zoom 2400..............................AT&C1&D2M0H0X1V1E0S2=1S0=0^M
Zoom Fax 9600.......................................ATS7=55S11=60^M
Zoom...................................AT&F2&C1&D2S0=0S2=1S95=3X1^M
Zuckerboard Model ZCom24/AT 2400....AT&C1&D2&T5M0V1E0Q0X1S2=1S0=0^M
Zyxel U-1496B..................................AT&FS2=1M0&Y2X6&W1^M
Zyxel U-1496E.........................AT&FS0=0S2=1M0V1E1H0X6S40=4^M
Page 147
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
APPENDIX B
----------
SPITFIRE QUESTIONS AND ANSWERS
------------------------------
QUESTION: Why is the "Do You Want ANSI Graphics? <y/N>" displayed
each time a caller logs on the BBS?
ANSWER: Some BBS software stores in the caller's file whether a
caller uses ANSI, and if so, then each time the caller logs
on, ANSI graphics are automatically displayed. When creating
SPITFIRE it was decided to provide the caller with the
opportunity to select the display preferred at each log-on.
There are two basic reasons for including this prompt to each
caller upon log on. First, some callers may call the BBS
from different locations. For instance, many callers call
the BBS from work as well as from home and while they may
have a color monitor at home, they may not at work. In such
a case, they would not want to use color graphics each time
they log-on. Also, observation has proven that a caller may
sometimes choose ANSI graphics and other times not. This may
be due to the amount of time a caller has to spend on the
board since ANSI graphics display slower than those created
in ASCII. For whatever their reasons may be, SPITFIRE
demonstrates increased flexibility by allowing the caller to
make that choice.
QUESTION: With SPITFIRE at the "Ready For Use..." prompt, the phone
rings and SPITFIRE simply does NOT answer the phone, but
rather stays at the "Ready For Use..." prompt. Why?
ANSWER: SPITFIRE relies on verbose result codes to determine an
incoming call, the baud rate of the incoming call and whether
the incoming call is an error correction modem. This problem
would indicate that the modem initialization string is not
correct. You should try using a different initialization
string. Your modem initialization string requires a V1 in it
because this tells your modem to send verbose result codes.
This manual contains a list of initialization strings which
have been tested and are reported to work with the various
modems listed. Also, please note, that the initialization
string must contain the numeric character 0 (zero) and NOT
the alphabetical character O.
Once you have discovered an initialization string that works
with your modem, please report said string and the complete
name and information pertaining to your modem so this
information can be added to this manual.
Page 148
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
QUESTION: When attempting to jump to DOS with the Alt+J command, the
screen blinks but nothing happens. What can be done to
rectify this?
ANSWER: Depending on the individual's system, occasionally the Alt+J
command which allows the Sysop to drop to DOS appears to be
inoperative. The situation can easily be corrected by
setting the path statement in your AUTOEXEC.BAT file so
SPITFIRE can locate COMMAND.COM thru your path.
QUESTION: Why am I unable to Drop To DOS from a remote location
using the Sysop Menu's Drop To DOS feature?
ANSWER: Some systems do not like to redirect their I/O through
a serial port. In such cases, the problem can often be
corrected by using a program written specifically for this
purpose. It is suggested you use either Doorway by Marshall
Dudley or Remdoor by Ken Brown. Both Doorway and Remdoor
incorporate remote drop to DOS capability and are available
for download from Buffalo Creek's BBS. Also, please bear in
mind, SPITFIRE releases control to the SFREMOTE.BAT file
during the remote drop to DOS and lies dormant in memory.
QUESTION: Documentation for external door installation refers to
a file called SFDOORS.DAT. I cannot find this file on
my drive. Was it neglectfully not included in my SPITFIRE
package?
ANSWER: When executing a door, SPITFIRE creates two files containing
pertinent caller information required for door operation.
These files are SFDOORS.DAT, required by SPITFIRE, and
DOOR.SYS, a universal format door caller information file.
These are only used during door operation and once the
caller returns to SPITFIRE, SFDOORS.DAT is automatically
erased. Similarly, SFMAIN.DAT, SFFILE.DAT and SFMESS.DAT
created during execution of the Main, File and Message
Menu's Sysop configurable command option are erased when
the caller returns to SPITFIRE.
QUESTION: When a caller uploads a file to "Sysop Only", how is the
Sysop made aware of the uploaded file?
ANSWER: SPITFIRE incorporates two techniques by which the Sysop
is notified that a file has been uploaded privately. A
message is written both in the CALLERS.LOG and also
the HEYSYSOP.LOG file that informs the Sysop that a file
Page 149
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
has been uploaded for "Sysop Only". The CALLERS.LOG and the
HEYSYSOP.LOG file can be viewed from the Sysop Menu and
by pressing F1 at the "Ready..." prompt. These files
should be checked regularly to keep the Sysop aware of the
various BBS activities.
QUESTION: When a caller logs on using the ANSI Color Graphics option,
when the SFFILES.BBS is displayed, occasionally a line in
the file is displayed only in the caller's default color.
Why is this?
ANSWER: In the event a file line is not colored like the others, but
rather uses the caller's default color, that is because the
comma in the file size is either not located properly or does
not exist. SPITFIRE cues off the comma in the file size to
determine the coloring of the SFFILES.BBS listings.
QUESTION: After successfully running SPITFIRE for sometime, all of
a sudden upon booting up, a message is displayed that the
SFNODE.DAT file was not found. Why did this happen?
ANSWER: When SPITFIRE is installed, a file named SFNODE.DAT is
created. This file contains information as to what drive
and directory the SPITFIRE system and work files exist.
If after using the program, the Sysop changes the location
of SPITFIRE (for example, SPITFIRE was originally booted up
on a floppy and then moved to Drive C), SPITFIRE will
continue to look for the files in the originally specified
location. The easiest way to rectify this situation is to
use the /P command line parameter to set the drive and
directory used in SPITFIRE. Another option would be to
erase the existing SFNODE.DAT file and allow a new one to
be created. SPITFIRE will automatically assign the default
path to the one in which SPITFIRE.EXE resides.
QUESTION: After adding new files to the various file areas for the
callers to download, I noticed that when a caller logs
onto the BBS and does a check for new files, these files
are not displayed. What is the problem?
ANSWER: There are basically two reasons this could happen. The
first being, it is possible the files were copied into the
download directories but not added to the appropriate
SFFILES.BBS file. Another possible explanation would be
Page 150
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
that the file name, file size, file date and file
description has not been located in the exact specified
place in the SFFILES.BBS. Refer to the section - SPITFIRE
FILE CLARIFICATIONS - of this manual for further information
regarding this subject.
QUESTION: Why are callers unable to view the contents of a ZIP file
after selecting <V>iew A File Archive from the File Menu?
ANSWER: This feature will only work with MS/PC DOS archive files.
It could be that the ZIP file in question was archived by a
system other than MS/PC DOS and then uploaded to your BBS.
QUESTION: The callers log reveals "Message sent and erased" for a
caller who logged onto the BBS. What does this mean?
ANSWER: This would depict a special notice ( <x>.BBS; refer to the
section - SPITFIRE FILE CLARIFICATION - of the manual for
further explanation regarding this subject) was left for a
specific caller. Once the caller receives this message it is
automatically erased. The CALLERS.LOG displays the above
mentioned message to inform the Sysop the message was sent
and then erased.
QUESTION: The HEYSYSOP.LOG reveals a message that a specific archived
file fails the CRC check. What does this mean?
ANSWER: Anytime the Sysop is notified that an archived MS/PC DOS file
fails the CRC check, this means that the specified file is
corrupt and should be erased from your system.
QUESTION: What is the purpose of the SPITFIRE.OVR overlay file?
ANSWER: By accessing the overlay file, many SPITFIRE procedures and
functions are called into memory only when they are needed
rather than being held in memory continuously. Thus the
overlay file drastically reduces the amount of memory which
is required to run SPITFIRE. This is very significant to
Sysops running SPITFIRE in a multi-tasking or networking
environment that is required for multi-node operation.
QUESTION: I recently registered a door program and was requested by
the author to add him to the caller's file. This was so he
could call the BBS and upload my registered version. The
Page 151
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
call was long distance and he wanted to avoid the time
required to complete the log-on questionnaire. Is it
possible to add a caller to the callers data base?
ANSWER: A caller may be added to the SFUSERS.DAT file by selecting
ALT+A at the SPITFIRE "Ready For Use..." prompt. A caller
may also be added by using the <U>... Modify Callers feature
found within the Sysop Menu.
QUESTION: Why does SPITFIRE limit the number of files allowed in
an external batch download to seven files and in an
external batch upload to six?
ANSWER: These limits are set by DOS rather than SPITFIRE. DOS
will only allow a command line to contain a specific
number of characters. The seven files for the batch
download and the path for the upload directory and the
six files allowed in a batch upload attain the allowable
DOS limits. SPITFIRE can be configured through the
UseFile feature to allow 99 files per download batch,
provided the external protocol has this capability.
QUESTION: When running SPITFIRE, I get a Runtime error 004 and
SPITFIRE stops. Why?
ANSWER: This runtime error problem is caused by too many files
being open at one time. You will need to increase the
number of files that DOS will allow to be opened at once
by changing your CONFIG.SYS file. Refer to your DOS
manual for further information regarding this subject.
Your system will have to be rebooted after changing your
CONFIG.SYS file.
QUESTION: Why am I able to upload files that are contained in the
SFNOUP.DAT file? As I understand this is a list of files
which should not be able to be uploaded to the BBS.
ANSWER: SFNOUP.DAT has no affect on any caller with Sysop status.
In other words, any caller with a security equal to or
greater than what you have designated as Sysop security
for your system may upload files, even though they may
be contained in your SFNOUP.DAT.
QUESTION: Why are callers unable to leave a comment to Sysop on my
BBS?
ANSWER: Before SPITFIRE will allow a comment to be left to a Sysop,
the Sysop must be a caller of the BBS. The name the Sysop
uses to log onto the BBS must be the same as the Sysop Caller
Page 152
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
Name configured using the ALT+Z configuration window. If a
Sysop enters Sysop as the Sysop Caller Name and then logs
onto the BBS using their real name, SPITFIRE will not allow
a comment to be left to the Sysop because Sysop is not a
caller of the BBS. In this example, the Sysop would need to
change the Sysop Caller Name from Sysop to their real name.
Once this is done SPITFIRE will allow comments to be sent to
the Sysop. In other words, the Sysop caller name must be the
same as the name used for logging onto the BBS.
QUESTION: I just updated my bulletin number #9, yet when a caller
logs on, SPITFIRE does not list bulletin number #9 as being
updated. Why?
ANSWER: For purposes of speed, SPITFIRE stops searching the drive
for new bulletins once a bulletin file is not found. For
example, let's say that SPITFIRE finds BULLET[1..7].BBS
and then does not find BULLET8.BBS. In such case, SPITFIRE
then stops the search and will not find BULLET9.BBS even
though it may exist on the drive. There are two ways to fix
this. The first and most logical way is to keep your
bulletins in numeric order. The second way would be to
create dummy bulletin files so SPITFIRE will find the dummy
file and continue its search for updated bulletins.
QUESTION: When attempting to boot SPITFIRE or when attempting to
log-on the BBS, I am told that a maintenance operation
is being performed and that I should call back later. There
is no maintenance operation being performed. What do I do?
ANSWER: This could be caused by a number of things which are not
important to discuss. The way to cure the problem is to
erase the SFWHOSON.DAT file found in the WORK directory.
When you reboot SPITFIRE, a new SFWHOSON.DAT will be created.
QUESTION: When I attempt to log-on SPITFIRE, I am told that I am
already logged on another node but I am not. What do I do?
ANSWER: This could be caused by a number of things which are not
important to discuss. The way to cure the problem is to
erase the SFWHOSON.DAT file found in the WORK directory.
When you reboot SPITFIRE, a new SFWHOSON.DAT will be created.
QUESTION: I cannot make sense of the information written to my
CALLERS.LOG. What is the problem?
Page 153
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
ANSWER: The file entitled, SFCALLOG.DAT, needs to be copied to the
directory you have configured as your WORK file path. This
file contains information which is used to write the
CALLERS.LOG. If this file is not found by SPITFIRE, your
CALLERS.LOG will be missing important information which
clarifies the recorded activity.
Thank you very much for selecting SPITFIRE.
Page 154
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
NOTES:
Page 155
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 1
<x>.BBS/CLR - 25, 26, 27, 28, 29, 33, 80, 117
19200 - 5, 6, 8, 113, 145, 146, 147
38400 - 5, 145, 147
1K-XMODEM - 75, 76, 98
<<<<<< A >>>>>>
ALL.BBS - 17, 25, 27, 33, 71
Alt+A - 36, 59, 63, 106, 152
Alt+C - 59, 61, 69
Alt+D - 59, 69, 102
Alt+E - 59, 69
Alt+F - 20, 26, 50, 58, 59, 62, 69
Alt+F1 - 26, 58, 62
Alt+F2 - 58, 62
Alt+F3 - 59, 62
Alt+J - 59, 69, 70, 102, 149
Alt+L - 36, 59, 70
Alt+M - 5, 6, 7, 8, 43, 59, 70, 113
Alt+P - 19, 21, 43, 59, 70, 119, 124, 129
Alt+Q - 59, 70, 71, 115
Alt+R - 20, 44, 59, 71
Alt+S - 7, 59, 71, 115
Alt+T - 12, 14, 55, 59, 66, 71, 93
Alt+Z - 11, 16, 26, 33, 34, 59, 71, 73, 79, 103, 107, 108, 127, 131,
132, 153
ANSI - 3, 15, 17, 25, 26, 27, 28, 29, 31, 32, 37, 58, 75, 76, 91, 94,
104, 105, 117, 148, 150
ANSI.SYS - 3, 17, 29
APPENDIX A - 4, 5, 144
APPENDIX B - 148
ARC - 4, 9, 11, 15, 18, 19, 32, 39, 50, 52, 53, 60, 67, 73, 78, 88,
90, 91, 92, 93, 94, 95, 96, 97, 98, 103, 107, 125, 151, 153
ARQ - 4, 5, 8, 9
ASCII - 6, 23, 31, 36, 37, 41, 42, 54, 76, 95, 98, 104, 105, 120,
125, 148
AUTOEXEC.BAT - 38, 44, 132, 149
<<<<<< B >>>>>>
BPS - 77
Backup Files - 42
BADINIT - 23, 40
Batch - 22, 23, 25, 26, 31, 32, 34, 38, 39, 40, 42, 44, 98, 99, 100,
101, 102, 111, 113, 119, 120, 121, 122, 123, 124, 125, 126,
127, 128, 129, 139, 140, 152
Page 156
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 2
Batch Download - 26, 31, 34, 99, 100, 121, 122, 123, 128, 129, 152
Batch Upload - 26, 31, 100, 101, 102, 126, 127, 152
Baud Rate - 4, 8, 10, 26, 42, 43, 70, 113, 120, 125, 130, 132, 148
BBSNAME - 25, 39
Beep - 40, 41
Binkleyterm - 130
BRK - 3, 4, 119, 120, 121, 123, 124, 125, 126, 129
BRK OFF - 119, 120, 121, 123, 124, 125, 126, 129
BRK ON - 119, 121, 123, 124, 126, 129
BRK.DRV - 3, 4
Buffalo Creek's BBS - 1, 20, 32, 35, 40, 42, 70, 97, 115, 116, 118,
121, 123, 126, 136, 137, 144, 149
BUFFERS - 3
Bulletins - 25, 27, 30, 66, 72, 73, 111, 115, 117, 153
BULLET<x>.BBS/CLR - 25
<<<<<< C >>>>>>
CALLERS.TMP - 23, 123
CALLERS.LOG - 10, 23, 24, 59, 61, 62, 105, 106, 107, 111, 149, 150,
151, 153, 154
SFCALLOG - 24, 154
Capture Chat To Disk - 58, 61
Cd-Rom - 15, 18, 19, 91, 97
Chat - 23, 25, 28, 32, 33, 34, 35, 58, 59, 60, 61, 62, 69, 72, 74,
75, 88, 95, 109, 133, 134, 135, 136, 137
CHATDONE - 25
Check Today's Statistics - 58, 61
Command Line Parameters - 5, 6, 42, 43, 140
COMMAND.COM - 4, 120, 125, 149
Conference - 15, 18, 20, 22, 24, 26, 27, 37, 42, 44, 45, 46, 47, 48,
49, 52, 59, 63, 65, 71, 73, 78, 79, 80, 81, 82, 83, 84,
85, 86, 87, 88, 102, 103, 104, 105, 107, 108, 113, 131,
138, 140
Configure - 4, 5, 6, 7, 9, 10, 11, 13, 14, 15, 16, 17, 18, 20, 24, 26,
27, 34, 35, 37, 42, 44, 45, 46, 48, 49, 50, 52, 53, 54,
55, 56, 59, 66, 69, 70, 71, 73, 77, 79, 82, 83, 85, 86,
89, 98, 103, 104, 105, 107, 108, 109, 110, 111, 112, 113,
114, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125,
126, 127, 129, 131, 132, 133, 136, 152, 153, 154
CONFIG.SYS - 3, 4, 17, 29, 152
CRC - 76, 98, 151
<<<<<< D >>>>>>
DAILYLMT.DAT - 12, 13, 14, 23, 28, 32, 33, 34, 35, 134, 137
Delete - 11, 42, 45, 46, 47, 48, 52, 63, 65, 69, 82, 84, 87, 88,
90, 107, 108, 111, 137
Page 157
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 3
DESQVIEW - 3, 136
Device - 3, 4, 17, 29
Disconnect Delay - 8, 10
Display - 4, 7, 8, 9, 10, 12, 13, 14, 15, 16, 17, 19, 20, 21, 23,
25, 26, 27, 28, 29, 31, 32, 33, 34, 35, 36, 37, 39, 40,
41, 42, 44, 46, 47, 48, 50, 52, 53, 55, 56, 57, 58, 60,
61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74,
75, 76, 77, 78, 79, 80, 81, 82, 83, 85, 86, 87, 88, 89,
90, 91, 92, 94, 95, 96, 97, 99, 100, 101, 103, 104, 105,
106, 107, 108, 109, 111, 115, 116, 117, 118, 119, 121,
122, 123, 124, 126, 128, 129, 130, 131, 132, 133, 148,
150, 151
Display File Path - 19
DLMT - 25
Doors - 4, 22, 31, 38, 72, 73, 114, 115, 116, 117, 136, 139, 149
DORBUL - 25, 27, 117
DOS - 1, 3, 4, 5, 11, 13, 22, 37, 38, 42, 43, 50, 51, 59, 62, 69,
70, 102, 103, 111, 115, 116, 120, 125, 132, 133, 139, 140,
149, 151, 152
Download - 2, 13, 14, 15, 23, 25, 26, 27, 28, 30, 31, 32, 33, 34,
35, 36, 37, 38, 40, 41, 42, 50, 51, 52, 53, 61, 63, 64,
75, 78, 79, 90, 91, 92, 93, 95, 97, 98, 99, 100, 115,
116, 118, 119, 120, 121, 122, 123, 126, 127, 128, 129,
137, 138, 139, 144, 149, 150, 152
DSZ - 3, 118, 119, 121, 122, 123, 124, 125, 126, 127
<<<<<< E >>>>>>
EDLIN - 31
EMS - 3, 4, 5, 8, 9, 10, 13, 20, 23, 34, 38, 43, 74, 77, 98, 105,
112, 117, 120, 121, 122, 125, 126, 130, 131, 136, 140, 144,
148, 149
Erase - 22, 23, 37, 40, 62, 63, 90, 91, 92, 94, 105, 111, 115, 120,
136, 149, 150, 151, 153
Eventime - 25
Events - 22, 38, 44, 59, 63, 69, 83, 103, 109, 110, 111, 112, 125,
127, 131
Exit - 59, 69, 70, 84, 93, 95, 110, 116
External Protocols - 118, 121, 123, 124, 126, 127, 128, 129
<<<<<< F >>>>>>
F1 - 26, 58, 59, 62, 144, 146, 150
F2 - 8, 10, 26, 29, 30, 58, 60, 62, 144, 145, 147
F3 - 18, 37, 58, 59, 60, 62, 91, 93, 145
F4 - 58, 61
Page 158
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 4
F5 - 58, 61
F6 - 58, 61
F7 - 58, 61
F8 - 58, 61
F9 - 58, 61
F10 - 58, 62
File Area - 15, 18, 20, 22, 26, 27, 37, 42, 44, 50, 51, 52, 53, 54,
59, 63, 66, 69, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99,
100, 101, 102, 103, 125, 127, 138, 150
File Tag - 90, 97
FILE<x>.BBS/CLR - 25, 27
FILST<x>.BBS/CLR - 26
Free File - 53, 138
Frontdoor - 130
<<<<<< G >>>>>>
GOODBYE - 8, 26, 55, 72, 75, 78, 89, 90, 91, 93, 94, 95, 99, 100,
101, 102, 103, 114, 115
<<<<<< H >>>>>>
Hardware - 3, 8, 9, 113
HEYSYSOP.LOG - 12, 17, 24, 56, 59, 62, 93, 105, 106, 107, 149,
150, 151
High Speed Async Routines - 8
<<<<<< I >>>>>>
Initialization String - 4, 5, 6, 7, 8, 9, 10, 42, 43, 70, 113,
144, 148
<<<<<< J >>>>>>
JOKER.DAT - 24, 26, 36, 65, 66
<<<<<< L >>>>>>
Lantastic - 3, 136
LOCKOUT.BBS/CLR - 26, 36
Loop - 111, 115, 116, 133
Page 159
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 5
<<<<<< M >>>>>>
Main Menu - 8, 16, 21, 22, 24, 26, 28, 31, 33, 37, 38, 54, 55, 57,
59, 67, 71, 72, 73, 77, 78, 88, 90, 96, 102, 106, 108,
114, 115, 116, 132, 133
MAIN<x>.BBS/CLR - 26
Maintenance - 27, 42, 63, 102, 104, 105, 133, 153
MAXUSERS - 12, 26
Message Conference - 20, 22, 24, 26, 27, 37, 42, 44, 45, 46, 47, 48,
49, 65, 71, 73, 78, 79, 80, 81, 82, 83, 84, 85,
86, 87, 88, 102, 103, 104, 105, 108, 113, 131, 140
Message Files Path - 19
MGLST<x>.BBS/CLR - 26, 80
MKSFMENU - 32
Modem - 3, 4, 5, 6, 7, 8, 9, 10, 20, 23, 39, 40, 42, 43, 59, 61, 62,
63, 69, 70, 71, 75, 76, 98, 113, 118, 121, 122, 123, 126,
128, 132, 144, 145, 146, 147, 148
Move - 2, 6, 8, 47, 48, 52, 53, 59, 62, 64, 84, 87, 88, 91, 92, 93,
94, 96, 99, 100, 101, 102, 105, 108, 112, 115, 125, 127, 150
MSG<x>.BBS/CLR - 26, 27
Multi-Tasking - 17, 131, 132, 136, 151
Multi-Node - 13, 23, 24, 25, 29, 34, 72, 74, 104, 105, 122, 131, 132,
133, 136, 151
MUV - 3
<<<<<< N >>>>>>
NEEDSYS.BBS/CLR - 26, 62
Network - 131, 132, 136, 145, 151
Net-Mail - 25, 39, 43, 45, 48, 82, 85, 108, 112, 113, 130, 131
Newsletter - 28, 37, 72, 74
NEWUSER.BBS/CLR - 16, 26
Node Chat - 23, 32, 33, 34, 35, 72, 74, 75, 109, 133, 134, 135,
136, 137
<<<<<< O >>>>>>
Old Message Purge - 45, 47, 48
<<<<<< P >>>>>>
Pack - 2, 6, 21, 23, 24, 25, 30, 32, 35, 36, 37, 38, 39, 40, 44, 47,
48, 62, 65, 69, 79, 82, 86, 102, 103, 104, 105, 113, 114,
115, 130, 132, 133, 137, 138, 139, 140, 146, 149
Pack Message - 102, 104, 140
PAK - 93, 98
Page 160
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 6
Password - 7, 8, 11, 13, 15, 16, 17, 27, 28, 29, 41, 63, 65, 66,
68, 71, 75, 76, 103, 104, 105, 116, 133
Paths - 19, 20, 21, 50, 59, 70, 129, 131
Preview Area - 50, 52
PRIVATE.BBS/CLR - 13, 17, 26
Protocols - 4, 19, 20, 21, 27, 28, 34, 42, 70, 95, 98, 99, 118,
119, 121, 122, 123, 124, 126, 127, 128, 129, 130
Purge Allowed - 63, 69
<<<<<< Q >>>>>>
Questionnaires - 24, 31, 54, 55, 74
Queue - 18, 78, 80, 87, 88, 99, 100, 101, 102, 121, 122, 123, 138
Quick Log - 23, 25, 33, 70
<<<<<< R >>>>>>
Ratio - 1, 5, 6, 8, 11, 12, 13, 14, 16, 20, 21, 22, 24, 28, 33, 34,
35, 42, 43, 49, 54, 66, 73, 93, 96, 108, 109, 110, 114, 117,
119, 124, 129, 131, 132, 133, 137, 141, 149, 151, 153
Registration - 1, 141
Result Message - 4, 8
<<<<<< S >>>>>>
Sealink - 3, 76, 98
SEC.BBS - 25, 27, 33, 40
SF.BAT - 6, 7, 22, 23, 38, 43, 44, 110, 111, 114, 115, 116, 117, 130
SF1STF - 26
SF1STM - 26
SF2SLOW - 10, 26, 29
SFASLEEP - 26
SFBATCHD - 26, 31, 32
SFBATCHU - 26, 31, 32
SFBBSLST.DAT - 25, 77
SFBDAY - 26
SFCHAT.CAP - 23, 61, 62
SFDOOR.Mnu - 22, 23, 31, 114, 115, 137
SFDOORS.DAT - 22, 115, 116, 136, 149
SFDORBAK - 27, 117
SFDORBUL - 27, 117
SFDOWN - 27
SFDR<x>.BBS/CLR - 27
SFEVENTS - 22
SFEXTDN - 27, 29, 34, 118, 119, 121, 122, 123, 128, 129
Page 161
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 7
SFEXTDN,<x>.BAT -
SFEXTUP - 27, 29, 123, 124, 126
SFEXTUP<x>.BAT -
SFFAREA - 7, 22, 42
SFFILE.BAT - 22, 23, 38
SFFILE.MNU - 21, 30, 31, 89, 116
SFFILES.BBS - 27, 29, 37, 51, 90, 91, 92, 93, 94, 95, 96, 97, 127,
138, 150, 151
SFFILE.DAT - 22, 136, 149
SFIMPEXP - 27, 31, 32, 91, 94
SFINIT.BAT - 4, 23, 39
SFLOGON.BAT - 23
SFLOG - 23, 110, 111
SFMAIN.BAT - 22, 23, 38, 77
SFMAIN.MNU - 21, 30, 31, 116
SFMAINT - 27, 104, 105, 133
SFMAIN.DAT - 22, 136, 149
SFMCONF - 7, 22, 42
SFMESS.BAT - 22, 23, 38, 89, 98
SFMESS.DAT - 22, 136, 149
SFMQDONE - 27
SFMSG.MNU - 21, 30, 31, 36, 116
SFMSGPCK - 4, 24, 25, 39, 113
SFNEWU - 24, 54, 56, 57, 59, 106, 107
SFNODE - 7, 22, 27, 150
SFNOTIME - 27
SFNOUP - 24, 25, 37, 90, 92, 94, 152
SFNWSLTR - 28, 37, 74
SFORDER.MNU - 23, 31, 57
SFORD<x>.BBS/CLR - 28
SFPAGED.BBS/CLR - 28, 39, 60, 74, 88, 95, 96
SFPRELOG.BBS - 28, 29, 71, 133
SFPROMSG.BBS/CLR - 28, 77, 118
SFPROTCO.HLP - 23, 95
SFRATIO.BBS/CLR - 28, 34, 35
SFREMIND.BBS/CLR - 28
SFREMOTE.BAT - 22, 23, 38, 103, 149
SFSEC<x>.BAT - 23, 39
SFSENDIT - 138
SFSYSOP.MNU - 21, 30, 31
SFSYSTEM - 7, 24
SFTIMEUP.BBS/CLR - 28
SFUP.BBS - 28
SFUPCASE.DAT - 16, 24, 25, 38
SFUSERS - 7, 14, 23, 24, 35, 40, 62, 63, 65, 68, 103, 105, 106,
138, 139, 152
SFWHOSON.DAT - 25, 132, 153
SF.BAT - 6, 7, 22, 23, 38, 43, 44, 110, 111, 114, 115, 116, 117, 130
SOP<x>.BBS/CLR - 28
Page 162
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 8
SPITFIRE.HLP - 23, 77, 89, 98
SPITFIRE.OVR - 21, 130, 151
SYSINIT - 28
Sysop Utilities - 72, 77, 78, 89, 90, 98, 102, 110, 112, 134
<<<<<< T >>>>>>
Telink - 76, 98
This System's Info - 72, 74
THOUGHTS.BBS - 28, 29, 42
Tilde - 10, 56
TOOMANY.BBS - 12, 28
<<<<<< U >>>>>>
Undelete - 11, 84, 108
Upload - 11, 12, 13, 14, 15, 17, 18, 23, 25, 26, 27, 28, 31, 34,
35, 36, 37, 39, 40, 41, 50, 51, 53, 61, 63, 64, 65, 75, 78,
79, 90, 93, 94, 95, 98, 100, 101, 102, 108, 110, 112, 123,
124, 125, 126, 127, 128, 138, 139, 149, 150, 151, 152
Usefile - 34, 122, 128, 129, 152
USERINIT.BBS/CLR - 28, 60
Utilities - 2, 38, 39, 50, 51, 72, 77, 78, 89, 90, 98, 102, 110,
112, 131, 134, 136, 138, 139, 141
<<<<<< W >>>>>>
WATCHDOG - 38
WELCOME1.BBS/CLR - 27, 29, 71, 133
WELCOME<x>.BBS/CLR - 29
Wildcards - 92, 95, 97
WILDFIRE - 3, 116
WINDOWS - 3, 136
Work Files Path - 19, 21
<<<<<< X >>>>>>
Xmodem - 75, 76, 98
Xpert - 63, 64, 72, 75, 78, 89, 90, 97, 102, 107
<<<<<< Y >>>>>>
Ymodem - 42, 70, 98
Ymodem-g - 42, 70, 98
Page 163
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
SUBJECT INDEX - Page 9
<<<<<< Z >>>>>>
ZIP - 16, 18, 35, 37, 79, 91, 93, 98, 115, 121, 126, 127, 138, 151
Zmodem - 118, 121, 122, 123, 126, 128
Page 164
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
NOTES:
Page 165
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
NOTES:
Page 166
----------------------------------------------------------------------
-+ SPITFIRE BULLETIN BOARD SYSTEM - Version 3.3 - March 3, 1993 +-
----------------------------------------------------------------------
NOTES: